🚀Bolt CMS is an open source, adaptable platform for building and running modern websites

Overview

Bolt 5 standard project skeleton

Bolt CMS is an open source, adaptable platform for building and running modern websites. Built on PHP, Symfony and more. Read the site for more info.

To check out Bolt and set up your first Bolt installation, read Installing Bolt 5.


Installing Bolt CMS

with Composer

Note: Installing with composer and running the site on your local machine using the method described below is the preferred method of the Bolt core development team.

You can set up a new Bolt 5 project, using the following command, replacing myprojectname with your desired project's name.

composer create-project bolt/project myprojectname

Navigate into the newly created folder, and configure the database in .env (The configuration is intended to work with the database SQLite).

# Configure database for doctrine/doctrine-bundle
# SQLite (note: _three_ slashes)
DATABASE_URL=sqlite:///%kernel.project_dir%/var/data/bolt.sqlite

# MYSQL / MariaDB
#DATABASE_URL=mysql://db_user:"db_password"@127.0.0.1:3306/db_name?serverVersion=5.7

# Postgres
#DATABASE_URL=postgresql://db_user:"db_password"@127.0.0.1:5432/db_name?serverVersion=11&charset=utf8

Set up the database, create the first user and add fixtures (dummy content):

bin/console doctrine:database:create # Create database
bin/console doctrine:schema:create # Create schema in database

bin/console doctrine:fixtures:load --no-interaction # Load fixtures in databse (step not compulsory)
bin/console bolt:add-user --admin # Follow the creation steps in the console (warning: fixtures already created an admin user)

composer run post-create-project-cmd # Duplicate themes in the appropriate folder

bin/console bolt:info # Verify Bolt installation

Run Bolt using the built-in webserver, Symfony CLI or your own preferred webserver:

bin/console server:start

or…

symfony server:start -d
symfony open:local

Finally, open the new installation in a browser. If you've used one of the commands above, you'll find the frontpage at http://127.0.0.1:8000/
The Bolt admin panel can be found at http://127.0.0.1:8000/bolt

Log in using the credentials you created when setting up the first user.

Note: If you don't want to use Docker, don't forget to remove what isn't necessary:
- remove .dockerignore file
- remove docker-composer.yml file
- remove Dockerfile file
- remove docker folder

with Docker

Disclaimer: Docker is not used by the Bolt core development team. Bolt can be run using docker, but you are advised to only attempt this if you have enough experience with Docker yourself to understand what is going on in the Dockerfile and in docker-compose.yml. The included setup might not be a good fit for your Dockerized setup. When in doubt, follow general advice on running Symfony projects in docker, as Bolt is built using Symfony. The Bolt team doesn't provide pre-built containers.

Start by downloading the Bolt project distribution .tar.gz file, or generate a GitHub repository from the template we provide. Once you have extracted its content, the resulting directory contains the Bolt project structure. You will add your own code and configuration inside it.

Note: Try to avoid using the .zip file, as it may cause potential permission issues.

Bolt is shipped with a Docker setup that makes it easy to get a containerized development environment up and running. If you do not already have Docker on your computer, it's the right time to install it.

On Mac, only Docker for Mac is supported. Similarly, on Windows, only Docker for Windows is supported. Docker Machine is not supported out of the box.

Open a terminal, and navigate to the directory containing your project skeleton.

Navigate into the newly created folder, and configure environment variables in the .env file for Docker & the database MySQL version 5.7.

###> symfony/framework-bundle ###
APP_ENV=dev
APP_DEBUG=1
APP_SECRET=!ChangeMe!
TRUSTED_PROXIES=127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16
TRUSTED_HOSTS='^(localhost|nginx)$'
###< symfony/framework-bundle ###

###> doctrine/doctrine-bundle ###
DATABASE_URL=mysql://bolt:!ChangeMe!@db:3306/bolt?serverVersion=5.7
###< doctrine/doctrine-bundle ###

###> symfony/mailer ###
MAILER_DSN=smtp://mailcatcher:1025
###< symfony/mailer ###

Run the following command to start all services using Docker Compose:

docker-compose up -d # Running in detached mode
docker-compose exec php bin/console doctrine:schema:create # Create schema in database
docker-compose exec php bin/console doctrine:fixtures:load --no-interaction # Load fixtures in databse (step not compulsory)
docker-compose exec php bin/console bolt:add-user --admin # Follow the creation steps in the console (warning: fixtures already created an admin user)

This starts the following services:

Name Description Port(s) Environment(s)
db A MySQL 5.7 database server 3306 all (prefer using a managed service in prod)
php The Bolt project with PHP, PHP-FPM 7.4, Composer and sensitive configs n/a all
nginx The HTTP server for the Bolt project (NGINX) 8080 all
h2-proxy A HTTP/2 and HTTPS development proxy for all apps 8443 dev (configure properly your web server in prod)
mailcatcher MailCatcher runs a super simple SMTP server delivered with a web interface 1025 for smtp port
1080 for interface
only for dev
To see the status of the containers, run:
docker-compose ps
To execute commands in a container, run:
docker-compose exec <container name> <command>
docker-compose exec php sh # To enter the container directly, you will be placed at the root of the project
docker-compose exec php bin/console bolt:add-user # Follow the creation steps in the console (warning: fixtures already created an admin user)
To see the container's logs, run:
docker-compose logs        # Display the logs of all containers
docker-compose logs -f     # Same but follow the logs
docker-compose logs -f php # Follow the logs for one container

Finally, open the new installation in a browser. If you've used one of the commands above, you'll find the frontpage at http://localhost:8080/ or https://localhost:8443/
The Bolt admin panel can be found at http://localhost:8080/bolt or https://localhost:8443/bolt

The tests

Static analysis

The ecs.php configuration file is located at the root of the cms project

# With Composer
composer lint                         # Launch ECS in dry run mode (command to launch in a Continuous Integration)
composer lint:fix                     # Launch ECS in fix mode

# With Docker
docker-compose exec php composer lint # Launch ECS by the php container

The phpstan.neon configuration file is located at the root of the cms project

# With Composer
composer phpstan                         # Launch PHPStan (command to launch in a Continuous Integration)

# With Docker
docker-compose exec php composer phpstan # Launch PHPStan by the php container

Contributing

If you'd like to contribute, please check Bolt's core repository and read the "Contributing to Bolt" documentation page.

Comments
  • Error when creating project

    Error when creating project

    $ composer create-project bolt/project bolt4
    
    ---- redacted... package installation went well ----
    
    Executing script cache:clear --no-warmup [KO]
     [KO]
    Script cache:clear --no-warmup returned with error code 1
    !!  
    !!  In AbstractMySQLDriver.php line 110:
    !!                                                                                 
    !!    An exception occurred in driver: SQLSTATE[HY000] [1698] Access denied for u  
    !!    ser 'root'@'localhost'                                                       
    !!                                                                                 
    !!  
    !!  In PDOConnection.php line 31:
    !!                                                                      
    !!    SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost'  
    !!                                                                      
    !!  
    !!  In PDOConnection.php line 27:
    !!                                                                      
    !!    SQLSTATE[HY000] [1698] Access denied for user 'root'@'localhost'  
    !!                                                                      
    !!  
    !!  cache:clear [--no-warmup] [--no-optional-warmers] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--] <command>
    !!  
    !!  
    Script @auto-scripts was called via post-install-cmd
    

    The installer shouldn't be trying to clear cache / connect to database before proper db credentials are setup. (Trying to use root user as default isn't the best idea either).

    opened by ADmad 18
  • Feat: add new docker for production & development environment

    Feat: add new docker for production & development environment

    • [x] add new docker-compose.yml & Dockerfile layer divisions
      • [x] service php & configuration (env PROD & DEV)
        • [x] use php:74-fpm-alpine
        • [x] add docker-healthcheck
        • [x] update docker-entrypoint
          • [x] use php.ini PROD or DEV
          • [x] create important folders for the use of the project (public/files, public/theme, public/thumbs, var/cache, var/log & var/sessions)
          • [x] install vendor for development environment
          • [x] test BDD is active
          • [x] use php bin/console bolt:info instead of launching after installing vendors (because it is looking for the version of the database which might not be launched in time)
          • [x] if the theme does not exist, it will copy it
          • [x] if this project use DoctrineMigrationBundle then launch migrations (all env) else reset & create schema (only env DEV & TEST)
          • [x] launch fixtures
      • [x] service nginx & configuration (env PROD & DEV)
        • [x] copy public folder of php container
      • [x] service db with MySQL 5.7 version (only env DEV)
      • [x] service h2-proxy to have SSL (only env DEV)
      • [x] service mailcatcher to do (only env DEV)
    • [x] add .dockerignore file
    • [x] add .editorconfig file
    • [x] replace .env.dist by .env file, to respect symfony's good practice
    • [x] rework the .gitignore file
    • [x] rework the Makefile file
    • [x] rework the README.md file
    • [x] rework the composer.json file & update dependencies
      • [x] bolt/core 4.0.1
      • [x] bolt/themes 3.3.2
    • [x] update the symfony.lock file
    • [x] fix the use of API-Platform
      • [x] the configuration (add path %kernel.project_dir%/src/Entity for the use of our own entity)
      • [x] install assets with the copy file
    • [x] add dev dependency for ECS & PHPStan
    • [x] upgrade documentation
    • [x] rework commit in pull request

    I added a CI for the installation of a Bolt project with Composer or Docker Compose.

    • [x] Bolt project installation test with docker-compose, PHP 7.4 and MySQL
      • [x] Validate composer.json
      • [x] Run PHP-CS-Fixer
      • [x] Run PHP-CS-Fixer with fix flag
      • [x] Run PHPStan
      • [x] Run Security Checker
      • [x] Check HTTP reachability
        • [x] http://localhost:8080
        • [x] http://localhost:8080/bolt
        • [x] http://localhost:8080/api/contents
        • [x] http://localhost:8080/api/fields
        • [x] http://localhost:8080/api/relations
        • [x] https://localhost:8443
        • [x] https://localhost:8443/bolt
        • [x] https://localhost:8443/api/contents
        • [x] https://localhost:8443/api/fields
        • [x] https://localhost:8443/api/relations
    • [x] Bolt project installation test with composer, PHP 7.4 and MySQL
      • [x] Validate composer.json
      • [x] Run PHP-CS-Fixer
      • [x] Run PHP-CS-Fixer with fix flag
      • [x] Run PHPStan
      • [x] Run Security Checker
      • [x] Check HTTP reachability
        • [x] http://localhost:8000
        • [x] http://localhost:8000/bolt
        • [x] http://localhost:8000/api/contents
        • [x] http://localhost:8000/api/fields
        • [x] http://localhost:8000/api/relations

    The continuous integration is not yet working on this pull request because nothing is merged into the Bolt repository yet in my opinion. On the other hand you can see it working on my pull request in my fork

    opened by toofff 14
  • Updating files to match Symfony updates

    Updating files to match Symfony updates

    Current setup doesn't allow to read .env files properly

    Instructions to create the bug:

    1. Remove .env from .gitignore (because we have .env.local for that)
    2. Add a .env.local to override values from .env
    3. .env has:
    DATABASE_URL=sqlite:///%kernel.project_dir%/var/data/bolt.sqlite
    
    1. .env.local has:
    DATABASE_HOST=localhost
    DATABASE_USERNAME=symfony
    DATABASE_PASSWORD=symfony
    DATABASE_NAME=symfony
    
    DATABASE_URL=mysql://${DATABASE_USERNAME}:${DATABASE_PASSWORD}@${DATABASE_HOST}:3306/${DATABASE_NAME}
    

    Now either running bin/console or opening the website will say either 'Malformed parameter &quot;url&quot;' (referring to doctrine.yaml) or something regards to not being able to find the parameter or SQL server.

    Or was there a reason to have these files specifically like they are?

    opened by JKetelaar 8
  • Feat: add CI with github action

    Feat: add CI with github action

    While waiting for the PR #31 to be merged I added a CI for the installation of a Bolt project

    • [x] Bolt project installation test with docker-compose, PHP 7.4 and MySQL
      • [x] Validate composer.json
      • [x] Run PHP-CS-Fixer
      • [x] Run PHP-CS-Fixer with fix flag
      • [x] Run PHPStan
      • [x] Run Security Checker
      • [x] Check HTTP reachability
        • [x] http://localhost:8080
        • [x] http://localhost:8080/bolt
        • [x] http://localhost:8080/api/contents
        • [x] http://localhost:8080/api/fields
        • [x] http://localhost:8080/api/relations
        • [x] https://localhost:8443
        • [x] https://localhost:8443/bolt
        • [x] https://localhost:8443/api/contents
        • [x] https://localhost:8443/api/fields
        • [x] https://localhost:8443/api/relations
    • [x] Bolt project installation test with composer, PHP 7.4 and MySQL
      • [x] Validate composer.json
      • [x] Run PHP-CS-Fixer
      • [x] Run PHP-CS-Fixer with fix flag
      • [x] Run PHPStan
      • [x] Run Security Checker
      • [x] Check HTTP reachability
        • [x] http://localhost:8000
        • [x] http://localhost:8000/bolt
        • [x] http://localhost:8000/api/contents
        • [x] http://localhost:8000/api/fields
        • [x] http://localhost:8000/api/relations

    The continuous integration is not yet working on this pull request because nothing is merged into the Bolt repository yet in my opinion. On the other hand you can see it working on my pull request in my fork

    opened by toofff 6
  • Composer update produces error: MetadataStorageError.php line 13

    Composer update produces error: MetadataStorageError.php line 13

    I installed Bolt via the project, and ran composer update.

    Initial results:

    Nothing to install, update or remove...
    [OK] Cache for the "prod" environment (debug=false) was successfully cleared...
    [OK] All assets were successfully installed...
    [OK] All assets were successfully installed...
    

    But then this error:

    11:44:43 CRITICAL  [console] Error thrown while running command "doctrine:migrations:up-to-date --ansi". Message: "The metadata storage is not up to date, please run the sync-metadata-storage command to fix this issue." ["exception" => Doctrine\Migrations\Exception\MetadataStorageError^ { …},"command" => "doctrine:migrations:up-to-date --ansi","message" => "The metadata storage is not up to date, please run the sync-metadata-storage command to fix this issue."]
    
    In MetadataStorageError.php line 13:
    
    The metadata storage is not up to date, please run the sync-metadata-storage command to fix this issue.
    
    doctrine:migrations:up-to-date [-u|--fail-on-unregistered] [-l|--list-migrations] [--configuration CONFIGURATION] [--em EM] [--conn CONN]
    
    
    [WARNING] Please run `php bin/console doctrine:migrations:migrate` to execute the database migrations.
    
    ⚙️  Bolt
    =======
    
     Bolt version: 5.0.0
    
     * Install type: Packaged distribution
     * Database: mysql 5.5.5-10.3.31-MariaDB-0ubuntu0.20.04.1 - Localhost via UNIX socket (with JSON)
     * PHP version: 7.4.3
     * Symfony version: v5.3.7
     * Operating System: Linux - 5.4.0-81-generic
    

    I ran bin/console doctrine:migrations:sync-metadata-storage and it was ok. I also did doctrine:migrations:migrate but there were no migrations to run.

    When I run composer update it shows same error again.

    opened by garrettboone 5
  • Problem when creating the project

    Problem when creating the project

    When doing composer create-project (with PHP7.4) I am getting this error:

    > php bin/console extensions:configure --with-config
    PHP Parse error:  syntax error, unexpected token "match" in /bolt/vendor/willdurand/negotiation/src/Negotiation/Negotiator.php on line 41
    Script php bin/console extensions:configure --with-config handling the post-install-cmd event returned with error code 255
    
    

    Any ideas?

    opened by ilukac 4
  • Mistake in composer.json in release 1.3.26

    Mistake in composer.json in release 1.3.26

    Hy,

    The dependencies in the version 1.3.26 are the dependencies from bolt 5 and not bolt 4

    "description": "Bolt 5 standard project skeleton",
        "license": "MIT",
        "require": {
            "bobdenotter/configuration-notices": "^1.0",
            "bobdenotter/weatherwidget": "^1.1",
            "bolt/article": "^1.0",
            "bolt/assets": "^5.0",
            "bolt/core": "^5.0",
            "bolt/newswidget": "^1.1",
            "bolt/redactor": "^1.0",
            "bolt/themes": "^3.3",
            "nelmio/security-bundle": "^2.10",
            "symfony/flex": "^1.6"
        },
    

    Link to the composer.json

    Maybe fix it could be a good option to let us install bolt 4 without having a bolt 5 beta project ^^

    opened by darkikim 4
  • No templates found on installation

    No templates found on installation

    I've just installed Bolt4, configured the database connection, run the set up script to configure the basics and install the fixtures.

    Then, when I access the URL in the browser I get the following error:

    Unable to find one of the following templates: "index.twig", "index.html.twig".

    It seems the entire templates directory is missing.

    duplicate 
    opened by benr77 4
  • Use of .env file by docker-compose has side-effect of copying it to the container

    Use of .env file by docker-compose has side-effect of copying it to the container

    In docker-compose.yml the .env file is used (specified with env_file) to configure a number of settings.

    Using .env this way has the 'side effect' of copying .env into the container. (Or at least, that is what I saw in a comment on https://github.com/docker/compose/issues/4140 - and it's the observed behavior by a bolt user on slack)

    The effect is that you can edit almost all files when using docker, and the changes will be picked up, but if you edit .env the changes will not be picked up by the container. That is quite confusing.

    I don't know if there is a real fix possible for this. A separate env file for docker with a comment explaining it won't be reloaded would be clear, but might mean duplication of config.

    opened by simongroenewolt 4
  • fix(dockerfile): change ttf-freefont by fonts-freefont-ttf debian pac…

    fix(dockerfile): change ttf-freefont by fonts-freefont-ttf debian pac…

    I try make docker-install This PR fix this errors: [x] Remove tf-freefont and add fonts-freefont-ttf [x] Run in node container make build-assets [x] Move in cd vendor/bolt/core && run npm rebuild node-sass in node container [x] Fix docker-db-create in php container [x] Add make docker-server in make docker-install [x] Add help in Makefile

    Error with tf-freefont: bolt-project-error-ttf-freefont

    opened by fabienChaillou 4
  • composer/composer requirement should be higher version

    composer/composer requirement should be higher version

    FYI: https://packagist.org/packages/composer/composer/advisories?version=5517140 v2.1.8 and lower have vuln

    I was able to locally modify composer.json with:

        "require": {
            "composer/composer": "^2.1.9",
            "composer/xdebug-handler": "^2.0",
            "php": ">=7.2.9 || ^8.0"...etc
    

    After composer update -W there were no composer conflicts.

    opened by garrettboone 3
  • /bolt page cannot be found on new install

    /bolt page cannot be found on new install

    Hi team,

    I've just done a new install of Bolt through the composer method and configured it to use MySQL. I'm able to load the frontend however I ran into these issues along the way:

    • Theme Base-2021 folder was empty on the initial attempt
      • This was solved by simply starting again and doing the composer install (now base-2018, base-2021 and skeleton are present)
    • .htaccess file does not accompany the install
      • Solved by just re-downloading from the install guide page

    One unsolved problem still exists:

    • /bolt is showing a 404 not found error

    Troubleshooting steps thus far:

    • Followed: https://docs.boltcms.io/5.0/installation/webserver/apache
      • There is no "RewriteBase" line in the Apache .htaccess file however I commented out the 2 lines that auto-determine and placed my own in there, no change, still not working

    Frontend here: http://3.232.63.252/ Backend 404: http://3.232.63.252/bolt

    It shouldn't be that I'm not using a domain, right?

    Other info: ⚙️ Bolt Bolt version: 5.1.18

    • Install type: Packaged distribution
    • Database: mysql 8.0.31-0ubuntu0.22.04.1 - Localhost via UNIX socket (with JSON)
    • PHP version: 7.4.33
    • Symfony version: v5.4.14
    • Operating System: Linux - 5.15.0-1023-aws
    • Memory limit: 1024M
    opened by JovinJovinsson 1
  • Outdated webpack encore package

    Outdated webpack encore package

    Is there a reason the NPM package for @symfony/webpack-encore is still locked to 0.30? They recently released version 4.0 of both the PHP and JS package. Are you open to PRs for these?

    opened by dreadnip 0
  • Strange installation issues, possibly related to odd installation path?

    Strange installation issues, possibly related to odd installation path?

    (Not sure if this has to do with me using ( and ) in paths or if it's something else.)

    Ubuntu 20.04.LTS.

    Issuing this: "php composer.phar create-project bolt/project Zap"

    Getting this:

    Installing bolt/project (2.2.7)

    There's a notice: "Package webmozart/path-util is abandoned, you should avoid using it. Use symfony/filesystem instead."

    And then, after doing some init work, I get this:

    Installing Bolt themes as hard copies.

    Theme Method / Error
    ✘ base-2021 Failed to remove directory "/sites/The_(very)Special_Site/Zap/public/theme/..Uu9": rmdir(/sites/The(very)_Special_Site/Zap/public/theme/..Uu9): Text file busy
    ✔ base-2018 copied
    ✔ skeleton copied

    [ERROR] Some errors occurred while installing themes.

    In BaseNode.php line 469: Invalid configuration for path "translation.configs.site.dirs.0": The directory "/sites/The_(very)_Special_Site/Zap/public/theme/base-2021" does not exist.

    In Configuration.php line 131: The directory "/sites/The_(very)_Special_Site/Zap/public/theme/base-2021" does not exist.

    2022-05-24T10:58:10+02:00 [info] User Deprecated: Method "Symfony\Component\HttpKernel\Bundle\Bundle::getContainerExtension()" might add "?ExtensionInterface" as a native return type declaration in the future. Do the same in child class "BabDev\PagerfantaBundle\BabDevPagerfantaBundle" now to avoid errors or add an explicit @return annotation to suppress this message.

    opened by joho1968 0
  • Fatal error, directory public does not exist

    Fatal error, directory public does not exist

    After uploading the website to the server, Bolt does not handle the public folder properly which was "public" on the local machine and is "public_html" on the server. clearing cache makes no difference. What am I looking at?

    Backend fatal error: PHP Fatal error: Uncaught Exception: The directory "/home//domains/website.com/public/theme/ThemeName" does not exist. in /home//domains/website.com/vendor/php-translation/symfony-bundle/DependencyInjection/Configuration.php:131\nStack trace:\n#0 /home//domains/website.com/vendor/symfony/config/Definition/Builder/ExprBuilder.php(239): Translation\Bundle\DependencyInjection\Configuration->Translation\Bundle\DependencyInjection\{closure}('/home/...')\n#1 /home//domains/website.com/vendor/symfony/config/Definition/BaseNode.php(461): Symfony\Component\Config\Definition\Builder\ExprBuilder::Symfony\Component\Config\Definition\Builder\{closure}('/home/...')\n#2 /home//domains/website.com/vendor/symfony/config/Definition/PrototypedArrayNode.php(177): Symfony\Component\Config\Definition\BaseNode->finalize('/home/...')\n#3 /home//domains/website.com/vendor/symfony/config/Definition/BaseNo in /home//domains/website.com/vendor/symfony/config/Definition/BaseNode.php on line 469\n

    opened by Seda145 3
  • Request, simple production deployment guide or automation?

    Request, simple production deployment guide or automation?

    I read the available documentation on how to configure Bolt for production but there is no complete list of what files are unrequired or unsafe to store on the production environment. I follow these steps to prepare my environment for uploading to the web host:

    Ensure:

    1. .env: change APP_SECRET to a random value, other than the default

    2. .env: set or add APP_ENV=prod

    3. .env: set or add APP_DEBUG=0

    4. Upload anything except the following:

    • ~/.vs/
    • ~/.vscode/
    • ~/.env.local
    • ~/.git/
    • ~/bin/post-create-project.php
    • ~/var/cache/
    • ~/var/data/ (if not used for sqlite)
    • ~/var/log/
    • Unused themes
    • Unused theme files (dev util js, Less / css maps, css var file generated from less, etc)
    • Any other remaining .local or local files must be compared to the Bolt documentation as they should not be committed (when working with other people) or in production.
    • Remaining developer files like vscode workspace file, executable files (bat etc) if present.

    So at this point I have no automation and do not know what should be removed from production. I checked the bolt/simple-deploy repo but see that it has issues and isn't well documented.

    Can I get a list of default files which should be removed after the initial installation and development process?

    opened by Seda145 0
Releases(2.2.19)
Owner
Bolt
Bolt
BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the project website for more information.

BaiCloud-cms About BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the

null 5 Aug 15, 2022
Question2Answer is a free and open source platform for Q&A sites, running on PHP/MySQL.

Question2Answer (Q2A) is a popular free open source Q&A platform for PHP/MySQL, used by over 22,000 sites in 40 languages.

Question2Answer 1.6k Jan 5, 2023
Statamic 3 - the flat-first, Laravel + Git powered CMS designed for building beautiful, easy to manage websites

Statamic 3 - the flat-first, Laravel + Git powered CMS designed for building beautiful, easy to manage websites

Statamic 600 Jan 4, 2023
Baicloud CMS is a lightweight content management system (CMS) based on PHP and MySQL and running on Linux, windows and other platforms

BaiCloud-cms About BaiCloud-cms is a powerful open source CMS that allows you to create professional websites and scalable web applications. Visit the

null 5 Aug 15, 2022
Free, open-source, self-hosted CMS platform based on the Laravel PHP Framework.

Winter is a Content Management System (CMS) and web platform whose sole purpose is to make your development workflow simple again. It was born out of

Winter CMS 1.1k Jan 3, 2023
Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS

Flextype is an open-source Hybrid Content Management System with the freedom of a headless CMS and with the full functionality of a traditional CMS. Building this Content Management System, we focused on simplicity. To achieve this, we implemented a simple but powerful API's.

Flextype 524 Dec 30, 2022
NukeViet 132 Nov 27, 2022
PHPVibe Open source video CMS / Video Sharing CMS / Youtube Api v3 / Video Embeds

PHPVibe Video CMS Free Video Sharing CMS The modern choice of design inspired by Youtube and a social videos sharing module that may just cut it for y

MediaVibe 71 Dec 18, 2022
Amila Laravel CMS - Free, open-source Simple Bootstrap Laravel CMS

Simple Bootstrap Laravel CMS. Support Laravel 8.x Can integrate into any existing Laravel project. Only add few database tables with prefixes, not affect your existing database tables. Support Laravel 7.x & Laravel 6.x & Laravel 5.x & MySql & PostgreSql - Amila Laravel CMS

Alex Zeng 96 Sep 6, 2022
Instructions and helpful files for running Drupal 7 on the Amezmo platform.

Drupal 7 Amezmo Instructions and helpful files for running Drupal 7 on the Amezmo platform. Description Drupal 7 requires some small modifications to

Steven DuBois 2 Aug 9, 2022
Wordpress plugin to allow websites to sell and distribute NFTs through the Enjin platform

MyMeta Basket is the world's first plug-and-play Wordpress/Enjin/Ethereum integration that allows you to start selling blockchain assets through your website within minutes. All you need is Wordpress, MyMeta Basket, and an Enjin subscription.

MyMetaverse 6 Oct 3, 2022
ExpressionEngine is a flexible, feature-rich, free open-source content management platform that empowers hundreds of thousands of individuals and organizations around the world to easily manage their web site.

ExpressionEngine CMS ExpressionEngine is a mature, flexible, secure, free open-source content management system. It is beloved by designers for giving

ExpressionEngine 412 Dec 27, 2022
HTMLy is an open source Databaseless Blogging Platform or Flat-File Blog prioritizes simplicity and speed written in PHP

HTMLy is an open source Databaseless Blogging Platform or Flat-File Blog prioritizes simplicity and speed written in PHP. HTMLy can be referred to as Flat-File CMS either since it will also manage your content.

Dan 858 Jan 6, 2023
Twill is an open source CMS toolkit for Laravel that helps developers rapidly create a custom admin console that is intuitive, powerful and flexible. /// Chat with us and others on Spectrum: https://spectrum.chat/twill

About Twill Twill is an open source Laravel package that helps developers rapidly create a custom CMS that is beautiful, powerful, and flexible. By st

AREA 17 3k Jan 6, 2023
True Multisite, Modern, Crazy Fast, Ridiculously Easy and Amazingly Powerful Flat-File CMS powered by PHP, Markdown, Twig, and Symfony

True Multisite, Modern, Crazy Fast, Ridiculously Easy and Amazingly Powerful Flat-File CMS powered by PHP, Markdown, Twig, and Symfony

null 4 Oct 28, 2022
phpReel is a free, MIT open-source subscription-based video streaming service that lets you create your platform for distributing video content in the form of movies or series.

phpReel is a free, MIT open-source subscription-based video streaming service that lets you create your platform for distributing video content in the form of movies or series.

null 118 Dec 14, 2022
Sulu is an open-source content management platform based on the Symfony PHP framework

This repository is no longer the recommended way to start a sulu project. Please have a look at the documentation to find out how to start a new proje

Sulu CMS 623 Nov 12, 2022
Zenphoto - a standalone CMS for multimedia focused websites

Zenphoto The simpler media website CMS http://www.zenphoto.org Welcome to the Zenphoto git repository! About Zenphoto is a standalone CMS for multimed

ZenphotoCMS 272 Dec 30, 2022
ProcessWire 3.x is a friendly and powerful open source CMS with a strong API.

Welcome to ProcessWire 3.x This document is in Markdown. An HTML formatted version of this document can be read at: https://github.com/processwire/pro

ProcessWire 804 Jan 3, 2023