Requirements

[dashohoxha]

• This container can be used to host and serve several websites. It does it through apache2 and its virtual host configurations.

• For each website there is a separate directory on /var/www/, for example /var/www/site1.example.org/, /var/www/site2.example.org/, etc.

• For each website there is a separate apache2 config file, which uses virtual domains.

• For each website the content is static HTML (no PHP, DB, etj.). This static HTML site is generated by jekyll.

• The container shares with the host the directories of the websites, the directory of apache config files, the apache logs, etc. This allows the user to work directly on the content of the websites from outside the container.

• After updating the content of a site, the user should run ds update <domain> in order to run jekyll and regenerate the content of the website.

• The user can also use the commands ds site-add <domain> and ds site-del <domain> in order to automate the creation and deletion of the sites (apache2 config files, etc.)

[JaydeepGo]

• Added separate config file and directory for every new added project which will be added through ds @jekyll project-add <project> and delete with ds @jekyll project-rm <project> <option "-r">.

• Individual config file add and delete done through ds @jekyll project-config-add <project> and ds @jekyll project-config-rm <project>.

• ds update <domain> already existed as ds @jekyll project-build <project> work same.

Again sorry for making you angry i think you are saying about complicated ds make process so i ask for optimize way. I reduce image size by removing apt cache.

One more thing i encounter a bug where i successfully build jekyll image. Now if i create and config the jekyll image and create container jekyll command give this error if run inside container screen-shot here

but if i run same image using docker application it rum smooth. Any suggestion??