2013-12-03 13:47:17 +00:00
# Froxlor
The server administration software for your needs.
Developed by experienced server administrators, this panel simplifies the effort of managing your hosting platform.
## Installation
### Fast install
1. Ensure that your webserver serves /var/www
2. Extract froxlor into /var/www
3. Point your browser to http://[ip-of-webserver]/froxlor
4. Follow the installer
5. Login as administrator
2016-12-17 13:31:07 +00:00
6. Adjust "System > Settings" according to your needs
7. Choose your distribution under "System > Configuration"
2013-12-03 13:47:17 +00:00
8. Follow the steps for your services
9. Have fun!
### Detailed installation
http://redmine.froxlor.org/projects/froxlor/wiki/Installationtarball
## Help
You may find help in the following places:
### IRC
froxlor may be found on freenode.net, channel #froxlor:
irc://chat.freenode.net/froxlor
### Forum
The community is located on http://forum.froxlor.org
### Wiki
More documentation may be found in the froxlor - wiki:
http://redmine.froxlor.org/projects/froxlor/wiki
## License
May be found in COPYING
## Downloads
### Tarball
http://files.froxlor.org/releases/froxlor-latest.tar.gz [MD5 ](http://files.froxlor.org/releases/froxlor-latest.tar.gz.md5 ) [SHA1 ](http://files.froxlor.org/releases/froxlor-latest.tar.gz.sha1 )
### Debian repository
[HowTo ](http://redmine.froxlor.org/projects/froxlor/wiki/Installationdebian )
/etc/apt/sources.list.d/froxlor.list
2016-01-24 21:15:44 +00:00
> deb http://debian.froxlor.org {wheezy|jessie} main
2013-12-03 13:47:17 +00:00
### Gentoo repository
[HowTo ](http://redmine.froxlor.org/projects/froxlor/wiki/Installationgentoo )
http://files.froxlor.org/gentoo/repositories.xml
2016-01-31 11:09:54 +00:00
2016-01-31 11:27:00 +00:00
## Let's Encrypt support
2016-01-31 11:09:54 +00:00
2016-01-31 15:03:10 +00:00
This version of Froxlor contains a test implementation of support for [Let's Encrypt ](https://letsencrypt.org ). This is (as Let's Encrypt is in itself)
still a beta version and may break your system. The way it currently works is by creating a (sub-)domain with the default system - certificate,
2016-01-31 11:09:54 +00:00
after which the Let's Encrypt cronjob orders the certificate for this (sub-)domain and inserts the certificates in the database. With the next run
of the default cronjob, the certificates will be updated on the disk and the webserver reloaded.
This has 2 known side-effects at the moment:
2016-01-31 11:27:00 +00:00
* The basic ip/port combinations don't work with the Froxlor - integration of Let's Encrypt, since it needs a certificate for the very first creation
2016-01-31 11:09:54 +00:00
* After creating a domain, it will have the default certificate for a short time (by default 5 minutes until the cronjob runs the next time)
2016-01-31 11:21:21 +00:00
It may be possible to fix these issues, but they are not a priority at the moment
