icalialabs / plis Goto Github PK

If Docker is not running on the machine, all you get now is:

Command:
%!(EXTRA string=docker-compose ps -q)Error:
%!(EXTRA *exec.ExitError=exit status 1)%  

Where it should explicitly say something like "It looks like Docker is not running on this machine!"

When you have a services with similar name, 'plis' match with the first coincidence.
Example

service:
    api_web:
   
    web:

If you want attach the 'web' service, you should run
plis attach web
but, 'plis' match with 'api_web' service

$ plis start web && plis attach web
docker-compose up -d web
back-end-3_postgres_1 is up-to-date
Creating back-end-3_web_1 ... done
No container running for service web

however

$ docker ps                                                                                                                                                                   
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                    NAMES
f13c0b362934       back_end:development   "/usr/src/bin/entryp…"   53 seconds ago      Up 53 seconds       0.0.0.0:3000->3000/tcp   back-end-3_web_1

I have other projects with pretty much the same docker-compose.yml where this DOES work, so I'm unsure of why it doesn't work in some others...

https://dev.to/defman/introducing-go-mod-1cdo

Somehow the new release changed the displayed output that is used by plis to parse project data when starting and attaching to containers...

Right now, the converted docker command is printed into the STDOUT.

This prevents us from doing something like:

echo "$(plis run web rails secret)" | docker secret create some_secret_base -

We need to output the converted command to the STDERR instead of the STDOUT.

For an easier/maintainable Linux installation I think it would be awesome to have a snap package for every release.

WHen updating via brew, the previous version is still active...

I like the idea of how npm allows tasks to be defined in the package.json file.

Currently at IcaliaLabs, when we use plis inside a project, the most executed tasks are these:

• plis run postgres restoredb some_database_name path/to/some/database.dump (Uses a script restoredb to restore a database from a dump file)
• plis run web rails db:migrate searchkick:reindex:all another:rake:task (Runs a bunch of rake tasks in a rails project)
• plis build service_a service_b service_c (Re-builds the dockerfiles referenced by the compose project)

Maybe we should be able to define these tasks in a file similar to how npm's package.json does.

IMPORTANT Having a config file must not be mandatory.

Would this file be a json? a YML?