George Baugh ebeedebb90 Better running on sock | 5 ay önce | |
---|---|---|
.github | 3 yıl önce | |
bin | 5 ay önce | |
config | 8 ay önce | |
etc | 8 ay önce | |
fail2ban | 6 ay önce | |
images | 3 yıl önce | |
lib | 5 ay önce | |
5 ay önce | ||
nginx | 5 ay önce | |
schema | 6 ay önce | |
service-files | 5 ay önce | |
t | 2 yıl önce | |
ufw | 5 ay önce | |
www | 5 ay önce | |
.gitignore | 5 ay önce | |
.perltidyrc | 10 ay önce | |
CHANGELOG | 3 yıl önce | |
Dockerfile | 2 yıl önce | |
Dockerfile.build | 3 yıl önce | |
Installer.mk | 5 ay önce | |
LICENSE | 3 yıl önce | |
Makefile.PL | 5 ay önce | |
Readme.md | 7 ay önce | |
call.pl | 8 ay önce | |
docker-exfil.sh | 3 yıl önce | |
dockerdeploy.sh | 3 yıl önce | |
fulldeploy.sh | 3 yıl önce | |
package-lock.json | 2 yıl önce | |
package.json | 2 yıl önce | |
profile.sh | 2 yıl önce | |
tcms | 5 ay önce | |
tcms-uwsgi | 5 ay önce |
A flexible perl CMS which supports multiple data models and content types
Deployment is currently:
Then:
starman -p $PORT www/server.psgi
OR (if you want tCMS as a systemd service for the current user):$PORT being whatever port you want it to sit on.
A Dockerfile and deployment scripts are provided for your convenience in building/running containers based on this:
# Build and run the server
./fulldeploy.sh
# Just run the server with latest changes
./dockerdeploy.sh
# Extract configuration & local data, then spin down the server
./docker-exfil.sh
The user guide is self-hosted; After you first login, hit the 'Manual' section in the backend.
Rate-Limiting is expected to be handled at the level of the webserver proxying requests to this application.
See migrate.pl, and modify the $docroot variable appropriately
Content templates are modular. Add in a template to /templates/forms which describe the content and how to edit it. Our post data storage being JSON allows us the flexibility to have any kind of meta associated with posts, so go hog wild.
Currently supported:
Planned development:
If you know a Post's ID (see the numbers at the end of it's URI when viewing it's permalink denoted by the chain emoji) You can embed template logic into your posts like so:
<: embed(12345, 'embed') :>
The first parameter is the ID number of the post. The second parameter is the formatting style:
These will be added as classes to the embedded post, so you can theme this appropriately.
Planned Development:
Starman and uWSGI
In production, I would expect you to run under uWSGI, and the tcms
command in the TLD runs this.
Otherwise, you can run www/server.psgi
to start starman normally.
domain picker at top -- manage all your web properties from one place
login and registration (forces email for a domain to allow posting on said domain) User data also stored in ES -- it's their profile page!
Error and Access logs immediately dumped into ES for EZ viewing in grafana
Automatic analytics!
Multiple auth models (ldap, oauth etc)
Builtin paywall -- add in LDAP users not on primary domain, give differing privs Have all content able to assign to paywall packages
One click share to social via oauth Mailing list blasts for paywall content