“C:\Program Files\Java\jdk1.6.0_45\bin\java.exe” \ -agentlib:jdwp=transport=dt_socket,address=9000,server=y,suspend=n \ -classpath .;”\E:\V1.0_ZJ\webmodel\otcp\cif\src\conf” \ “-Djava.ext.dirs=\E:\V1.0_ZJ\webmodel\otcp\cif\src\lib” MainClass rem Listening for transport dt_socket at address: 9000 rem jpda program started
linux则是"./catalia.sh jpda start"。看catalia.bat 和 catalia.sh的区别,大致相同jpda参数是
JPDA_TRANSPORT (Optional) JPDA transport used when the "jpda start"
command is executed. The default is "dt_socket".
JPDA_ADDRESS (Optional) Java runtime options used when the "jpda start"
command is executed. The default is 8000.
JPDA_SUSPEND (Optional) Java runtime options used when the "jpda start"
command is executed. Specifies whether JVM should suspend
execution immediately after startup. Default is "n".
The Java Debugger, jdb, is a simple command-line debugger for Java classes. It is a demonstration of the Java Platform Debugger Architecture that provides inspection and debugging of a local or remote Java Virtual Machine.
Starting a jdb Session
There are many ways to start a jdb session. The most frequently used way is to have jdb launch a new Java Virtual Machine (VM) with the main class of the application to be debugged. This is done by substituting the command jdb for java in the command line. For example, if your application’s main class is MyClass, you use the following command to debug it under JDB:
C:> jdb MyClass
When started this way, jdb invokes a second Java VM with any specified parameters, loads the specified class, and stops the VM before executing that class’s first instruction.
Another way to use jdb is by attaching it to a Java VM that is already running. A VM that is to be debugged with jdb must be started with the following options. These options load in-process debugging libraries and specify the kind of connection to be made.
You can then attach jdb to the VM with the following commmand:
C:> jdb -attach jdbconn
…
Note that “MyClass” is not specified in the jdb command line in this case because jdb is connecting to an existing VM instead of launching a new one.
There are many other ways to connect the debugger to a VM, and all of them are supported by jdb. The Java Platform Debugger Architecture has additional documentation on these connection options. For information on starting a J2SE 1.4.2 or early VM for use with jdb see 1.4.2 documentation
-rwxr-xr-x. 1 root root 17992 Nov 18 2015 /usr/lib64/libgmpxx.so.4.1.0
ldconfig
接着安装,竟然可以
1
2
3
4
5
cabal install HUnit
Resolving dependencies...
Configuring HUnit-1.3.1.1...
Building HUnit-1.3.1.1...
Installed HUnit-1.3.1.1
然后 testloop 编译不过去了
cabal install testloop
Resolving dependencies...
Configuring testloop-0.1.1.0...
Building testloop-0.1.1.0...
Failed to install testloop-0.1.1.0
Build log ( /root/.cabal/logs/testloop-0.1.1.0.log ):
Configuring testloop-0.1.1.0...
Building testloop-0.1.1.0...
Preprocessing library testloop-0.1.1.0...
[1 of 6] Compiling System.TestLoop.Internal.Signal ( src/System/TestLoop/Internal/Signal.hs, dist/build/System/TestLoop/Internal/Signal.o )
[2 of 6] Compiling System.TestLoop.Util ( src/System/TestLoop/Util.hs, dist/build/System/TestLoop/Util.o )
[3 of 6] Compiling System.TestLoop.Internal.Types ( src/System/TestLoop/Internal/Types.hs, dist/build/System/TestLoop/Internal/Types.o )
[4 of 6] Compiling System.TestLoop.Internal.Watcher ( src/System/TestLoop/Internal/Watcher.hs, dist/build/System/TestLoop/Internal/Watcher.o )
[5 of 6] Compiling System.TestLoop.Internal.Cabal ( src/System/TestLoop/Internal/Cabal.hs, dist/build/System/TestLoop/Internal/Cabal.o )
[6 of 6] Compiling System.TestLoop ( src/System/TestLoop.hs, dist/build/System/TestLoop.o )
src/System/TestLoop.hs:47:23:
Couldn't match type `FS.FilePath' with `[Char]'
Expected type: FilePath
Actual type: FS.FilePath
In the second argument of `treeExtExists', namely
`(FS.decodeString path)'
In a stmt of a 'do' block:
treeExtExists
manager
(FS.decodeString path)
"hs"
(reloadTestSuite moduleName modulePath paths)
src/System/TestLoop.hs:49:23:
Couldn't match type `[Char]' with `FS.FilePath'
Expected type: FilePath -> IO ()
Actual type: FS.FilePath -> IO ()
In the fourth argument of `treeExtExists', namely
`(reloadTestSuite moduleName modulePath paths)'
In a stmt of a 'do' block:
treeExtExists
manager
(FS.decodeString path)
"hs"
(reloadTestSuite moduleName modulePath paths)
cabal: Error: some packages failed to install:
testloop-0.1.1.0 failed during the building phase. The exception was:
ExitFailure 1
NodeBB Forum Software is powered by Node.js and built on either a Redis or MongoDB database. It utilizes web sockets for instant interactions and real-time notifications. NodeBB has many modern features out of the box such as social network integration and streaming discussions, while still making sure to be compatible with older browsers.
Additional functionality is enabled through the use of third-party plugins.
Collaborative system for managing documents, projects, customer relations and emails in one place
在线编辑文档
客户关系管理
邮件服务
文档管理
项目管理
ONLYOFFICE Community Server is a free open source collaborative system developed to manage documents, projects, customer relationship and email correspondence, all in one place.
Cross platform solution: Linux, Windows
Document management
Integration with Google Drive, Box, Dropbox, OneDrive, OwnCloud
File sharing
Document embedding
Access rights management
Customizable CRM
Web-to-lead form
Invoicing system
Project Management
Gantt Chart
Milestones, task dependencies and subtasks
Time tracking
Automated reports
Blogs, forums, polls, wiki
Calendar
Email Aggregator
People module (employee database)
Instant Messenger
Support of more than 20 languages
Running Docker Image
sudo docker run -i -t -d -p 80:80 onlyoffice/communityserver
This command will install ONLYOFFICE Community Server and all the dependencies it needs.
Configuring Docker Image
###Auto-restart
To make Docker auto-restart containers on reboot, please use the –restart=always in the docker run command:
sudo docker run -i -t -d -p 80:80 --restart=always onlyoffice/communityserver
Storing Data
All the data are stored in the specially-designated directories, data volumes, at the following location:
/var/log/onlyoffice for ONLYOFFICE Community Server logs
/var/www/onlyoffice/Data for ONLYOFFICE Community Server data
/var/lib/mysql for MySQL database data
To get access to your data from outside the container, you need to mount the volumes. It can be done by specifying the ‘-v’ option in the docker run command.
Access to the onlyoffice application can be secured using SSL so as to prevent unauthorized access. While a CA certified SSL certificate allows for verification of trust via the CA, a self signed certificates can also provide an equal level of trust verification as long as each client takes some additional steps to verify the identity of your website. Below the instructions on achieving this are provided.
To secure the application via SSL basically two things are needed:
Private key (.key)
SSL certificate (.crt)
So you need to create and install the following files:
When using CA certified certificates, these files are provided to you by the CA. When using self-signed certificates you need to generate these files yourself. Skip the following section if you are have CA certified SSL certificates.
Generation of Self Signed Certificates
Generation of self-signed SSL certificates involves a simple 3 step procedure.
STEP 1: Create the server private key
1
openssl genrsa -out onlyoffice.key 2048
STEP 2: Create the certificate signing request (CSR)
You have now generated an SSL certificate that’s valid for 365 days.
Strengthening the server security
This section provides you with instructions to strengthen your server security. To achieve this you need to generate stronger DHE parameters.
1
openssl dhparam -out dhparam.pem 2048
Installation of the SSL Certificates
Out of the four files generated above, you need to install the onlyoffice.key, onlyoffice.crt and dhparam.pem files at the onlyoffice server. The CSR file is not needed, but do make sure you safely backup the file (in case you ever need it again).
The default path that the onlyoffice application is configured to look for the SSL certificates is at /var/www/onlyoffice/Data/certs, this can however be changed using the SSL_KEY_PATH, SSL_CERTIFICATE_PATH and SSL_DHPARAM_PATH configuration options.
The /var/www/onlyoffice/Data/ path is the path of the data store, which means that you have to create a folder named certs inside /app/onlyoffice/CommunityServer/data/ and copy the files into it and as a measure of security you will update the permission on the onlyoffice.key file to only be readable by the owner.
You are now just one step away from having our application secured.
Available Configuration Parameters
Please refer the docker run command options for the --env-file flag where you can specify all required environment variables in a single file. This will save you from writing a potentially long docker run command.
Below is the complete list of parameters that can be set using environment variables.
ONLYOFFICE_HTTPS_HSTS_ENABLED: Advanced configuration option for turning off the HSTS configuration. Applicable only when SSL is in use. Defaults to true.
ONLYOFFICE_HTTPS_HSTS_MAXAGE: Advanced configuration option for setting the HSTS max-age in the onlyoffice nginx vHost configuration. Applicable only when SSL is in use. Defaults to 31536000.
SSL_CERTIFICATE_PATH: The path to the SSL certificate to use. Defaults to /var/www/onlyoffice/Data/certs/onlyoffice.crt.
SSL_KEY_PATH: The path to the SSL certificate’s private key. Defaults to /var/www/onlyoffice/Data/certs/onlyoffice.key.
SSL_DHPARAM_PATH: The path to the Diffie-Hellman parameter. Defaults to /var/www/onlyoffice/Data/certs/dhparam.pem.
SSL_VERIFY_CLIENT: Enable verification of client certificates using the CA_CERTIFICATES_PATH file. Defaults to false
MYSQL_SERVER_HOST: The IP address or the name of the host where the server is running.
MYSQL_SERVER_PORT: The port number.
MYSQL_SERVER_DB_NAME: The name of a MySQL database to be created on image startup.
MYSQL_SERVER_USER: The new user name with superuser permissions for the MySQL account.
MYSQL_SERVER_PASS: The password set for the MySQL account.
Installing ONLYOFFICE Community Server integrated with Document and Mail Servers
ONLYOFFICE Community Server is a part of ONLYOFFICE Community Edition that comprises also Document Server and Mail Server. To install them, follow these easy steps:
STEP 1: Create the ‘onlyoffice’ network.
1
docker network create --driver bridge onlyoffice
Than launch containers on it using the ‘docker run –net onlyoffice’ option:
Alternatively, you can use an automatic installation script to install the whole ONLYOFFICE Community Edition at once. For the mail server correct work you need to specify its hostname ‘yourdomain.com’.
STEP 1: Download the Community Edition Docker script file
STEP 2: Install ONLYOFFICE Community Edition executing the following command:
1
bash opensource-install.sh -md yourdomain.com
Or, use docker-compose. For the mail server correct work you need to specify its hostname ‘yourdomain.com’. Assuming you have docker-compose installed, execute the following command:
