/FrameworkBenchmarks

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ported Mojolicious setup to bash, added app.conf, added stop.sh for symmetry #1244

Merged
merged 1 commit into from Dec 16, 2014

Conversation

Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@jberger @msmith-techempower
@jberger
Contributor

jberger commented Nov 26, 2014

No description provided.

@jberger
ported Mojolicious setup to bash, added app.conf, added stop.sh for s… 
…ymmetry

PATH variable doesn't seem to work

carton handles PATH on its own

use hypnotoad with explicit perl interpreter

need carton full path to hypnotoad

updated dependencies
3e8383c
frameworks/Perl/mojolicious/stop.sh
HYPNOTOAD=$(${PERL_HOME}/bin/carton exec which hypnotoad)
${PERL_HOME}/bin/carton exec ${PERL_HOME}/bin/perl ${HYPNOTOAD} -s ${TROOT}/app.pl

This comment has been minimized.

Show comment
Hide comment
@msmith-techempower

msmith-techempower Dec 1, 2014

Member

There is no need for a stop.sh file; the meganuke branch uses a testrunner user and forcibly kills any/all processes started by that user via sudo killall -s 9 -u testrunner instead of calling a configured stop. You can delete this file safely.
Copy link
@msmith-techempower

msmith-techempower Dec 1, 2014

Member

There is no need for a stop.sh file; the meganuke branch uses a testrunner user and forcibly kills any/all processes started by that user via sudo killall -s 9 -u testrunner instead of calling a configured stop. You can delete this file safely.
@msmith-techempower

This comment has been minimized.

Show comment
Hide comment
@msmith-techempower

msmith-techempower Dec 1, 2014

Member

The bash_profile.sh can have a PATH environment variable set in it, but the setup.sh does not have access to it (or the usual home directory and a few others).

You can still set the PATH variable if you need something to be in it, but you will want to do it in your setup.sh file now.
Member

msmith-techempower commented Dec 1, 2014

The bash_profile.sh can have a PATH environment variable set in it, but the setup.sh does not have access to it (or the usual home directory and a few others).

You can still set the PATH variable if you need something to be in it, but you will want to do it in your setup.sh file now.

@msmith-techempower msmith-techempower merged commit 3e8383c into TechEmpower:meganuke Dec 16, 2014
1 check passed

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details

msmith-techempower added a commit that referenced this pull request Dec 16, 2014

@msmith-techempower
Merged jberger's branch for #1244
26cde54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment