forked from projects/fipamo
The official repo for Fipamo
ro
234453b900
the back up process did not include saving document and video assets so that needed to be updated to save all of those references along with images once that was done, the restore process had to be updated to look for docs and videos and create the corresponding directories to move them too the script responsible for moving those assets was also streamlined so a seperate process was not needed for each asset type. the last update date in the settings template was displaying incorrectly, so that was fixed as well. |
||
|---|---|---|
| app | ||
| bootstrap | ||
| config | ||
| content/themes/fipamo-default-v2 | ||
| database | ||
| public | ||
| resources | ||
| routes | ||
| storage | ||
| tests | ||
| .babelrc | ||
| .editorconfig | ||
| .env.example | ||
| .eslintrc | ||
| .gitattributes | ||
| .gitignore | ||
| .php-cs-fixer.php | ||
| .prettierignore | ||
| .prettierrc | ||
| artisan | ||
| composer.json | ||
| composer.lock | ||
| LICENSE | ||
| package.json | ||
| phpunit.xml | ||
| README.md | ||
| vite.config.js | ||
Fipamo means to save
The Fipamo project was born from a need for a simple, easy to use no data blog platform that doesn't require much effort to set up and maintain. Fipamo uses Markdown to handle posts and renders them to flat html so you can serve them from anywhere. No complicated set ups. No long list of dependencies. Just set up and go.
Because it's the 21 century. This should be easy.