apache-ensite
Apache 2 configuration file management a la debian
Why?
Having recently started movign away from Ubuntu I found that their way of managing apache configuration files still made sense, so I wrote this small bit of python to allow me to have a2ensite and a2dissite available on a FreeBSD system.
Huh?
The basic theory is to have a sites-available directory where you create the configuration files. When you want to actually use the configurations you enable them by creating a symlink from the sites-available directory to the sites-enabled directory. When you have finished using the configuration file, you simply remove the symlink. It makes things a lot easier and using these 2 small scripts make things even simpler.
How?
When you first install Apache on FreeBSD there are no sites-available or sites-enabled directories and the default configuration lacks the required directive, so either create the directories manually and then edit the httpd.conf file, or run
$ sudo a2ensite --setup
After creating a configuration file, e.g. blah.conf, you can enable it by
$ sudo a2ensite blah
When finished with the configuration file, e.g. blah.conf, simply run
$ sudo a2dissite blah
If you can't remember the filename simply run with no name (or use the --list command) and a list will be displayed.
$ a2ensite --list
*** You are not running with root privileges, so changes may not be possible.
apache24 installation in /usr/local/etc/apache24
Configuration File Enabled?
======================================== ==========
000-default.conf True
svn.conf False
Notes
- More than one file can specified at once.
- Matches are done using fnmatch so standard wildcards are available.
Metadata
Release files for apache-ensite 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| apache-ensite-0.2.2.tar.gz | 5.2 kB | Without provenance | Details for apache-ensite-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apache_ensite-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for apache_ensite-0.2.2-py3-none-any.whl |
Total release size: 11.6 kB
Release files / apache-ensite-0.2.2.tar.gz
| Download URL | apache-ensite-0.2.2.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
338a51fb6c2e70ada833d0a63be07005f2db38218fe5b4877192b9aea1520af6
|
|
BLAKE2b-256 checksum How to use checksums |
3b7aa1e0f7d2a0feb050f95cf1fc7c495f9eff3440d7b07e5cc809613d07e14c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.5
|
Release files / apache_ensite-0.2.2-py3-none-any.whl
| Download URL | apache_ensite-0.2.2-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ca71c1e3166dc7d977e9e8283cdd4f6c7ec3d65b50d841568de0f9616ce40395
|
|
BLAKE2b-256 checksum How to use checksums |
99aded277cf2a417ee5345e6a6742b4d37f80dcf713454d61d2ba5a1cde03157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.5
|
Security for apache-ensite 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.