Distributing, installing, updating and uninstalling software applications are common tasks in all enterprises. These tasks include a lot of processes and usually take up a lot of administrators' time and resources. Each of these tasks has to be completed in individual computers. The Software Deployment feature in Desktop Central enables administrators to distribute, install, update and uninstall software applications remotely as well as automatically. Features The Software Deployment feature in Desktop Central enables you to complete the following tasks:.
Create a repository of packages. This enables administrators to re-use packages any number of times to install or uninstall the software applications. Deploy both MSI and EXE-based software applications. Use the set of predefined templates to deploy software applications.
Perform pre-deployment activities for software installation/ uninstallation. Install software applications as a specific user using the Run As option.
Copy the installables to computers before installing software applications. Schedule deployment of software applications.
Uninstall MSI and EXE-based software applications. Desktop Central's Windows Installer feature improves the administrator's productivity by supporting remote MSI & EXE software/application deployment. Desktop Central can automatically install MSI & EXE software to users or computers at a scheduled time. Desktop Central supports software installation to users and computers or mass installation to OUs, Domains and Sites. Creating Software Repositories Software repositories are used to store software packages. These packages can either be for MSI-based software applications or EXE-based software applications. A software package added in Desktop Central will have the location of the installation files along with the installation and uninstallation commands.
A package once added can be used to deploy the software any number of times by just defining a configuration. Pre-Deployment Activities For ensuring a smooth and successful software deployment, Desktop Central provides the option to validate a set of conditions before a software installation/ uninstallation. The pre-deployment activities include checking for previous software versions, running processes of dependant executables, free disk space etc. Upon validation of each of these conditions, you can decide on proceeding with or skipping the installation/ uninstallation.
Scheduled Software Deployment Desktop Central allows administrators to schedule a software deployment to users and computers after a specified time. This is very useful in deploying the software after business hours to ensure users/computers are not affected due to this deployment. The network traffic will also be minimum at off hours. Visibility on Software Installation Status Desktop Central does not stop with just installing MSI/EXE software in the user machines; it also provides the status of the installation for the administrator to check whether the installation was successful in all the configured systems.
The software installation status is made available in the Desktop Central client, which can be accessed from anywhere in the network through a web browser. Uninstalling MSI and EXE-based Software In addition to installation of Windows software, Desktop Central also provides an ability to uninstall the MSI software applications that have been installed using Desktop Central.
The details of the installed software are maintained under the configurations. The administrator can just open the configuration, edit it and choose to remove the software that was previously installed. For more details, refer to the topic in the online help. Deploying Software Applications Using Templates The Templates tab in the Software Deployment section comprises of predefined applications that you can use to create packages automatically. This functionality downloads binaries from the respective vendors' websites to create packages automatically.
You can create a single package or multiple packages from the Templates tab and deploy them to target computers.
Steps to install OpenProject on Debian 8 (Jessie) All steps need to be run as root. Import the packager.io repository signing key Import the PGP key used to sign our packages. Since we're using the packager.io platform to distribute our packages, both package source and signing key are tied to their service. Wget -qO- sudo apt-key add - 2. Install apt-https suppport Since we only provide https package sources, you may need to install apt-transport-https as a preliminary step. Apt-get install apt-transport-https 3.
Add the OpenProject package source sudo wget -O /etc/apt/sources.list.d/openproject-ce.list 4. Install the OpenProject Community Edition package Using the following commands, apt will check the new package source and install the package and all required dependencies. Apt-get update apt-get install openproject. Steps to install OpenProject on Debian 9 (Stretch) All steps need to be run as root. Import the packager.io repository signing key Import the PGP key used to sign our packages. Since we're using the packager.io platform to distribute our packages, both package source and signing key are tied to their service.
Wget -qO- sudo apt-key add - 2. Install apt-https suppport Since we only provide https package sources, you may need to install apt-transport-https as a preliminary step. Apt-get install apt-transport-https 3.
Add the OpenProject package source wget -O /etc/apt/sources.list.d/openproject-ce.list 4. Install the OpenProject Community Edition package Using the following commands, apt will check the new package source and install the package and all required dependencies.
Apt-get update apt-get install openproject. Steps to install OpenProject on Ubuntu 14.04 Trusty All steps are prepended with sudo to ensure execution as the root user.
Import the packager.io repository signing key Import the PGP key used to sign our packages. Since we're using the packager.io platform to distribute our packages, both package source and signing key are tied to their service. Wget -qO- sudo apt-key add - 2. Ensure that apt-transport-https is installed Our repository requires apt to have https support. Install this transport method with sudo apt-get install apt-transport-https if you did not already.
Add the OpenProject package source sudo wget -O /etc/apt/sources.list.d/openproject-ce.list 4. Install the OpenProject Community Edition package Using the following commands, apt will check the new package source and install the package and all required dependencies. Apt-get update apt-get install openproject. Steps to install OpenProject package on Ubuntu 16.04 Xenial All steps are prepended with sudo to ensure execution as the root user. Import the packager.io repository signing key Import the PGP key used to sign our packages.
Since we're using the packager.io platform to distribute our packages, both package source and signing key are tied to their service. Wget -qO- sudo apt-key add - 2. Ensure that apt-transport-https is installed Our repository requires apt to have https support.
Install this transport method with sudo apt-get install apt-transport-https if you did not already. Add the OpenProject package source sudo wget -O /etc/apt/sources.list.d/openproject-ce.list 4. Install the OpenProject Community Edition package Using the following commands, apt will check the new package source and install the package and all required dependencies. Apt-get update apt-get install openproject. Package configuration The last step to your OpenProject installation is the configuration wizard.
It will set up the connection to a database and configure the application according to your environment. The OpenProject installation wizard currently supports the automatic setup for MySQL databases only. However, OpenProject itself supports both MySQL and PostgreSQL.
To configure the package to use an existing database, see the section below. To install or configure a MySQL database, skip to Configuration. The OpenProject package is configured through ENV parameters that are passed to the openproject user.
You can read the current ENV parameters with openproject run env. To write/read individual parameters, use openproject config:set PARAMETER=VALUE and openproject config:get PARAMETER. For instance if you wanted to change the session store you would do: sudo openproject config:set SESSIONSTORE=activerecordstore This is handy to configure options that are not available in the installer (yet). In most cases though, you should always try to configure the application first. Configuring for an existing a PostgreSQL database The MySQL wizard of the OpenProject installer internally sets the DATABASEURL (See in the Rails Guides for more information). You can set this DATABASEURL parameter yourself to either a MySQL or PostgreSQL database URL. Openproject config:set DATABASEURL='postgresql://user:password@host:port/dbname?param1=value1&.
Then, when configuring the addon, select skip in the MySQL installation wizard. The database specified using the URL will be used by Rails automatically for preparing the database. You can use these ENV parameters to customize OpenProject. Package configuration After the installation of the OpenProject package the system has to be configured to use this package and operate the OpenProject application. Therefore the package includes a configuration wizard which can be started using the following command: openproject configure Side note: The installer supports the configuration of necessary SSL connections too. If required the corresponding SSL certificates (incl. Keys) have to be placed somewhere on the machine before running the installer (or reconfigure the application later to enable the SSL support).
After you have completed the configuration wizard, the OpenProject instance will be started automatically. You can log into the instance initially with the user/password combination admin/admin. You will be asked to change this password immediately after the first login. Managing your OpenProject installation The openproject package comes with a command line tool to help manage the application. To see all possible command options of this tool you can run: admin@openproject-demo:# sudo openproject Usage: openproject run COMMAND options openproject scale TYPE=NUM openproject logs -tail -n NUMBER openproject config:get VAR openproject config:set VAR=VALUE openproject reconfigure In the rest of this section we'll go over some of the most important commands.
Run commands like rake tasks or rails console The openproject command line tool supports running rake tasks and known scripts like the rails console: sudo openproject run console # or a rake task sudo openproject run rake db:migrate # or check the version of ruby used by openproject sudo openproject run ruby -v Show logs The command line tool can also be used to see the log information. The most typically use case is to show/follow all current log entries. This can be accomplished using the the –tail flag. See example below: sudo openproject logs -tail You can also find all the logs in /var/log/openproject/. Reconfigure the application At any point in time, you can reconfigure the whole application by re-running the installer with the following command: sudo openproject reconfigure The command above will bring up the installation wizard again.
Please be aware that it will start the configuration/installation process from scratch. You can choose to modify existing entries, or just leave them as they are if you want to reuse them (note that passwords will appear as 'blank' entries in their respective input fields, but you don't need to enter them again if don't want to modify them).
Note that if you've just updated your OpenProject version, you should run openproject configure (see section below), which would automatically reuse your previous configuration, and only asks for your input if new configuration options are available. Installing plugins Note: this guide only applies if you've installed OpenProject using our DEB/RPM packages. Exist for use with OpenProject. Most plugins that are maintained by us are shipping with OpenProject, however there are several plugins contributed by the community. Previously, using them in a packaged installation was not possible without losing your changes on every upgrade. With the following steps, you can now use third party plugins.
Note: We cannot guarantee upgrade compatibility for third party plugins nor do we provide support for them. Please carefully check whether the plugins you use are available in newer versions before upgrading your installation. Add a custom Gemfile If you have a plugin you wish to add to your packaged OpenProject installation, create a separate Gemfile with the Gem dependencies, such as the following: group:opfplugins do gem 'openproject-emoji', git: ':branch = 'op-5-stable' end The group:opfplugins is generally recommended, but only required for plugins with custom frontend code that is picked up by webpack and output into their respective bundles. We suggest to store the Gemfile under /etc/openproject/Gemfile.custom, but the choice is up to you, just make sure the openproject user is able to read it. Propagate the Gemfile to the package You have to tell your installation to use the custom gemfile via a config setting: openproject config:set CUSTOMPLUGINGEMFILE=/etc/openproject/Gemfile.custom 3. Re-run the installer To re-bundle the application including the new plugins, as well as running migrations and precompiling their assets, simply re-run the installer while using the same configuration as before. Openproject configure Using configure will take your previous decisions in the installer and simply re-apply them, which is an idempotent operation.
It will detect the Gemfile config option being set and re-bundle the application with the additional plugins. Frequently asked questions - FAQ How can I install an OpenProject plugin? Our has instructions on how to customize your OpenProject installation. Please note that customization is not yet supported for Docker-based installations. How to migrate from Bitnami to the official OpenProject installation packages?
Please follow the following steps:. Make a dump of your bitnami MySQL database to export your data. You can refer to the. Make a dump of files your might have uploaded. You can refer to the to perform a full dump. Copy both dumps to the server you want to install OpenProject on.
Examples Of Open Source Software
Install OpenProject using the packaged installation. Import the MySQL dump into your new MySQL database. You can get your MySQL configuration by running sudo openproject config:get DATABASEURL. Extract the bitnami backup, and copy your file assets into the relevant directory (e.g. In /var/db/openproject/files for uploaded files). Restart OpenProject Can I use NginX instead of Apache webserver?
Yes, but you will lose the ability to enable Git/SVN repository integration. Note that the OpenProject installer does not support NginX, so you will have to ask to disable the Apache2 integration when running the installer, and then configure NginX yourself so that it forwards traffic to the OpenProject web process (listening by default on 127.0.0.1:6000). Can I use PostgreSQL instead of MySQL? Yes, but you will need to setup the database by yourself, and then ask the installer to use an existing database and enter the host and credentials configuration to access it. My favorite linux distribution is not listed. What can I do? You can either try the manual installation, or ask in the forum whether this could be added to the list of supported distributions.
Microsoft windows 8 1 pro build 9600 activation key. What is the better option to run OpenProject in production environments: docker or linux packages? Linux packages are currently the most stable option, since they are regularly tested and provide an installer to help you configure your OpenProject installation.
Docker images do not get the same level of testing. How to upgrade my OpenProject installation? Please refer to the documentation at What skills should I have for the installation?
If you use the packaged installation, you should have a basic knowledge of Linux and the command-line terminal. If you use the docker images, you need to be familiar with Docker and Docker volumes. Why don't you support Windows? Ruby support on Windows is notoriously difficult, however you might be able to run the Docker image, or use the unofficial Windows stack provided. How to backup and restore my OpenProject installation? Please refer to the documentation at How can I install a free SSL certificate using let's encrypt? You can get an SSL certificate for free via Let's Encrypt.
Open Source Software
Here is how you do it using: curl /usr/local/bin/certbot-auto chmod a+x /usr/local/bin/certbot-auto certbot-auto certonly -webroot -webroot-path /opt/openproject/public -d openprojecct.mydomain.com This requires your OpenProject server to be available from the Internet on port 443 or 80. If this works the certificate ( cert.pem) and private key ( privkey.pem) will be created under /etc/letsencrypt/live/openproject.mydomain.com/. Configure these for OpenProject to use by running openproject reconfigure and choosing yes when the wizard asks for SSL. Now this Let's Encryt certificate is only valid for 90 days.
Open Source Software For Windows
To renew it automatically all you have to do is to add the following entry to your crontab (run crontab -e): 0 1. certbot-auto renew -quiet -post-hook 'service apache2 restart' This will execute certbot renew every day at 1am. The command checks if the certificate is expired and renews it if that is the case. The web server is restarted in a post hook in order for it to pick up the new certificate.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |