Can't get it to work about porter

[BenQoder]

This has been fixed in v0.0.5

[PhiloNL]

Hi @BenQoder,
Please check cat ~/.porter/supervisord.log for more information.
You can also see individual logs cat ~/.porter/logs/haayaa-app.log.

[BenQoder]

I figured the reason why this is happening is because my command is something like

cd path/to/projects/haayaa & php artisan serve

The path my porter.yml file is is different from where my project is

Thus the reason why I created this pr to handle situations where we need to set custom directory.
#11

[dragonfire1119]

@BenQoder I had the same issue, but I ran "porter init" in each directory, then added my services and "porter add". By "porter status," you can easily examine all the services in each app.

@PhiloNL Nice work on this. I'm using it for my next.js project as well.

[BenQoder]

@dragonfire1119 your suggestion works and that's how I currently use this package.

But for situations where you need all your services for one workspace in a single porter.yml file we need an alternative.

It will be really uneasy for projects with up to 4 or 5 services to have multiple porter.yml files.

I hope you understand me.

[dragonfire1119]

@BenQoder I looked at how porter was constructed, and it writes to a "supervisord.conf," which sets a "directory=" and then calls the command. As a result, @PhiloNL would have to change the directory parameter to custom.

UPDATE:
Just saw you PR.