Skip to content
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

[Second life ?] 1.4 support #17

Open
ilan-schemoul opened this issue Jan 6, 2017 · 7 comments
Open

[Second life ?] 1.4 support #17

ilan-schemoul opened this issue Jan 6, 2017 · 7 comments

Comments

@ilan-schemoul
Copy link

ilan-schemoul commented Jan 6, 2017

As dev showed in another issue brieve signal of a desire of updating this repo I open this issue to say that first thing to do is to stop using root as user, or to use the --allow-superuser option when launching meteor otherwise meteor is not gonna working (either to compile or to watch file in dev mode) giving the error message :

You are attempting to run Meteor as the 'root' superuser. If you are
developing, this is almost certainly *not* what you want to do and will likely
result in incorrect file permissions. However, if you are running this command
in a build process (CI, etc.), or you are absolutely sure you know what you are
doing, set the METEOR_ALLOW_SUPERUSER environment variable or pass
--allow-superuser to proceed.

I also want to know what is the future of this package, multiple updates on docker has been made but github hasn't been updated. As there's activity on this package I'm probably gonna use this dockerfile if your going to support this package in the future so could you please declare for devs like me your plans about this package.

@ilan-schemoul
Copy link
Author

I may create a PR with a fix or create another repo, it's all about if @DanielDent is still active.

@DanielDent
Copy link
Owner

DanielDent commented Jan 7, 2017

A good PR will be appreciated and merged. Currently going through existing issues and I'm going to look at merging and what updates are needed. Thanks for your patience - I know it's been a long time since this repo was updated.

@ilan-schemoul
Copy link
Author

https://github.com/DanielDent/docker-meteor/blob/master/latest/meteor-installer.patch
Why is there stuff as
@@ -41,7 +46,7 @@

-if [ "$UNAME" != "Linux" -a "$UNAME" != "Darwin" ] ; then
+if [ "$UNAME" != "Linux" ] ; then

inside the sourcecode, it look like a git diff but it is inside the source code.

@DanielDent
Copy link
Owner

DanielDent commented Jan 8, 2017

It's used to adjust the installer so that it supports installing a specific version.

@ilan-schemoul
Copy link
Author

No I do not asked for an explanation 'bout this line I ask you why in source code (EVEN when one download it locally so it's not only a diff visible on github) :
image

This look like a diff between two version of a file but when I download your source code of https://github.com/DanielDent/docker-meteor/blob/master/latest/meteor-installer.patch I still have these kind of diff lines.
Anyway I don't know if I'm gonna code code these days but the fix is easy (tested), you add a --allow-superuser after the meteor command

@ilan-schemoul
Copy link
Author

Still I have a question, I'm not against helping but why do you update docker's repo but not Github's one ?

@ilan-schemoul
Copy link
Author

ilan-schemoul commented Jan 14, 2017

I think I'm going to give up w/ docker and use another way of deployment as pm2-meteor or something else. Anyway as I said I tested it and just add --allow-superuser when needed for instance

ONBUILD RUN meteor build .. --directoryy --allow-superuser \
[...]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants