yiendos / my-sites-ide Goto Github PK

Still have legacy code floating about, most noticeably in the Restart command.

We need to update the README with more precise steps about running globally, not just from checkout.

We need to hook up packagist.

At present .github/workflows is in the main repository, these folders and files should be extracted on setup.

Whoops db has worked its way into the Wordpress commands. This is only useful for inter-docker container communication. db_host should in fact be 127.0.0.1

Well this whole thing came from docker integration into CI systems. Let's at least demonstrate through github actions how easy it is to set up this process.

Plus provide a toggle to remove the php module and reload the service

So we've got loads of plugins that we could develop, lets experiments and see how we can extend the base functionlity of the IDE via a plugin architecture.

Just to make things a bit more fun, lets introduce one example application set of commands:

 wordpress
  wordpress:create  Create a WordPress site
  wordpress:delete  Nuke an existing site
  wordpress:vhost   Creates a new Apache2 and/or Nginx virtual host

These already exist under the dashboard project, lets launch them here.

For another demo

You know trying to set up nfs file sharing and dnsmasq localhost names is all well and good, but it ties us heavy into the Mac OS operating system, and docker is supposed to be ubiquitous across the platform. Therefore learning lessons from:
#3

Strip away any further fluff that will just make it harder for people to test out my-sites-ide.

The scripts can still be shared around, via wiki knowledge / help section. But it will be up to the end user to configure to their needs

Give Johan a demo of a Joomla! + page site

At present the use of /Sites/ and /Projects is mandatory. If the ide is meant to be a pluggable infrastructure not all clients will want that folder structure.

So instead of hardcoding both folders, how about we scan the site for a hidden folder.

.my-site-sites

.my-sites-projects 

Finding this file in a folder will set Sites and Projects dynamically.

With the current configuration of xdebug, it really isn't that easy to jump in and out of xdebug mode. By starting with ever requests IDE's often get stuck in a loop. By using a configuration that makes use of additional request params provided by:
https://chrome.google.com/webstore/detail/xdebug-helper/eadndfjplgieldjbigjakmdgkmoaaaoc?hl=en

It is easy to jump in and out of debug mode.

At present we are creating images per my-sites-ide project... pretty soon you'll land up with lots of images.

When we call mysites setup. We should look to see whether the base images exist:

• mysites_apache
• mysites_nginx
• mysites_php_fpm

If they do not exist, well go ahead and create them. If they do exist and -b option is passed in:

mysites setup -b

Then the base images will be re-built.

Therefore the docker-compose.yml file that we create on setup shouldn't contain build, but rather image declarations.

Because set up [project-name] setup could be done within the same folder _mysites and the my-sites-ide is a checked out version from the repository, it is possible to attempt to copy the _mysites into the very same _mysites folder. Recursion city.

Prevent this bug from happening.

Following on from waseem's testing, the only part of the stack that fails for ARM chips is the mysql:5.7 image. Seems that support for ARM has only come for mysql:8.0+:
https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-d5ba356f580dce71bebfc9fb0cd29b446cfb3aedff699fa9a1e34c2ffc88dd13?context=explore

This does have some knock on consequences for joomla:
https://docs.joomla.org/Joomla_and_MySQL_8

But nothing we can't get passed.