code-ops-show / writefully-old Goto Github PK

we use site-id to identify which content belongs to which sites.

if we delete the content or rename the folder the content should be deleted from the DB as well.

the listen gem gives support for detecting diffs in files, we can add this as a member of a set in redis when the message comes in via the listen gem and then before we upload the assets we do a check to see of the asset is a member of the set in redis. if it is we pop the item from the redis set and upload the asset.

this will improve the speed of content updating.

Right now some parts of the gem needs the rails environment to be loaded. Thats a big waste of memory

We can slim this down by eliminating the need for rails environment.

Maybe we just load the model to use the active record connection instead of loading the entire environment? still need to experiment if this is possible or not.

we need to be able to accept web hook from github to notify writefully of changes

writefully will then need to download the release? or just do a git pull from a branch to load the new content in.

eventually we want to support other content sources as well.

Right now our architecture already separates content source from the conversion process. so theoretically someone could write adapters for any source of content dropbox, box.net, copy.com, google drive and basically update content using any of those services.

The web hook must queue the job for some sort of worker that will pull and refresh content from github

Writefully should be able to manage multiple sites, 1 repository for 1 site.

We need to have some sort of template for people who want to quickly get started with writefully

When a theme is created it creates a repo in github.

Themes are updated via github repo as well

in the future themes can be uploaded and Writefully will correctly manage / activate them.

Basically when a site is created we need to create a repository in github with some sample content users can pull down

• user creates a site using the writefully/sites/new
• once the repo is created it needs to be saved to the Site
• we need to add the hook to the repo
• use rails controller to receive hook payload for simplicity and less dependency
• mountable hopefully via config.ru of the main rails app
• rails process and writefully can communicate via ZMQ

• indexes content into elasticseach for powerful search capability

since we support multi-site we need to handle the content of each site in the content folder.

we need to detect changes in content meta data