暂无描述

George S. Baugh 66b490ed58 handle docx content correctly 5 年之前
.github d5bab21dcd Create Funding.yml 5 年之前
bin ce50645529 Fix #113: Index flat-file posts with sqlite 5 年之前
config b12546fa1d tCMS 2.0: Now with more perl 5 年之前
data b12546fa1d tCMS 2.0: Now with more perl 5 年之前
lib 84735b282e Fix #143 5 年之前
schema b64ad3018c Fix #128: Remove usage of superfluous user identifier in auth 5 年之前
www 66b490ed58 handle docx content correctly 5 年之前
.gitignore 583861f887 Ignore HTTP DCV dirs 5 年之前
CHANGELOG b12546fa1d tCMS 2.0: Now with more perl 5 年之前
Dockerfile 054ad10fe9 make dockerfile work on centos 5 年之前
LICENSE b12546fa1d tCMS 2.0: Now with more perl 5 年之前
Makefile 14d28c5bf8 Fix #140 5 年之前
Readme.md 54d718bcb3 update readme w/dockerfile instrucciones 5 年之前

Readme.md

tCMS

A flexible perl CMS which supports multiple data models and content types

Deployment is currently:

  • make depend
  • make install
  • Set up proxy rule in your webserver
  • open tmux or screen
  • starman -p $PORT www/server.psgi

A Dockerfile is provided for your convenience in building images based on this: sudo docker build -t troglodyne:tcms sudo docker run -dp 5001:5001 troglodyne/tcms:latest starman -p 5001 www/server.psgi

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.

Migration of tCMS1 sites

See migrate.pl, and modify the $docroot variable appropriately

Content Types

  • Microblogs
  • Blogs
  • Video
  • Audio
  • Files
  • About Pages

Planned development:

  • Presentations
  • Test Plans / Issues (crossover with App::Prove::Elasticsearch)

Data Models

  • DUMMY - A JSON blob. Used for testing mostly, but could be handy for very small sites.
  • Flat File - Pretty much the tCMS1 data model; a migration script is forthcoming

Planned Development:

  • Elasticsearch - Documents are ideally indexed in a search engine, should be nice and fast too.
  • Git - More for the APE crossover

Ideas to come:

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