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

Nodejitsu shutting down. Modifications for new host. #635

Merged
merged 6 commits into from
May 30, 2015
Merged

Nodejitsu shutting down. Modifications for new host. #635

merged 6 commits into from
May 30, 2015

Conversation

sizzlemctwizzle
Copy link
Member

Well the Joyent team that maintains Nodejitsu got purchased by Goddady to develop their website builder. The result is that Nodejitsu is shutting down in August. I've moved the site to a new host and made the necessary modifications to the code. The site is likely more portable as a result. openuserjs.org is currently running on this branch.

@sizzlemctwizzle sizzlemctwizzle added the PR READY This is used to indicate that a pull request (PR) is ready for evaluation. label May 28, 2015
@Martii Martii added this to the #425 milestone May 28, 2015
@Martii
Copy link
Member

Martii commented May 28, 2015

I suggest giving this a couple of days running on production before merge to keep the transition of dev source here clean... I'll run some more tests in dev/local pro to ensure everything appears to be working with my available authentication mechanisms and tests. I'll halt dep update testings until this is done. e.g. this should be blocking for a few days. (to uncover any hidden boogs). Thanks btw. :)

@sizzlemctwizzle
Copy link
Member Author

I plan on canceling my nodejitsu subscription on Sunday so I don't get
billed for June. We can wait until then to merge.
On May 28, 2015 1:20 PM, "Marti Martz" [email protected] wrote:

I suggest giving this a couple of days running on production before merge
to keep the transition of dev source here clean... I'll run some more tests
in dev/local pro to ensure everything appears to be working with my
available authentication mechanisms and tests. I'll halt dep update
testings until this is done. e.g. this should be blocking for a few days.


Reply to this email directly or view it on GitHub
#635 (comment)
.

@sizzlemctwizzle sizzlemctwizzle added the BLOCKING Concentrate on bug fixes primarily. label May 28, 2015

var sessionStore = new MongoStore({ mongooseConnection: db });

// Force HTTPS
if (app.get('port') === 443) {
if (app.get('securePort')) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sizzlemctwizzle
So you are doing this programmatically now from the environment now instead of what was done at 932d1c9 ? e.g. which no longer allows http://openuserjs.org ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you don't set the SECURE_PORT environment variable then it runs using
http on PORT.
On May 29, 2015 3:48 AM, "Marti Martz" [email protected] wrote:

In app.js
#635 (comment)
:

var sessionStore = new MongoStore({ mongooseConnection: db });

// Force HTTPS
-if (app.get('port') === 443) {
+if (app.get('securePort')) {

@sizzlemctwizzle https://github.com/sizzlemctwizzle
So you are doing this programmatically now from the environment now
instead of what was done at 932d1c9
932d1c9
? e.g. which no longer allows http://openuserjs.org ?


Reply to this email directly or view it on GitHub
https://github.com/OpenUserJs/OpenUserJS.org/pull/635/files#r31308229.

@Martii
Copy link
Member

Martii commented May 29, 2015

Had to reset file owner perms on dynamicly generated CSS at .../public/less/bootstrap/oujs.css

We may need to watch that.

See also:

@Martii
Copy link
Member

Martii commented May 29, 2015

Reset timezone to UCT (UTC)... better for most log rotation around daylight savings time switch... note not all logs are showing this change and may be configured/initialized elsewhere... might need a restart of the server instead of a restart of the project. I'll leave that up to you for the moment... (btw project restarts appear killer fast :) ... plus moment and DB may pull from this clock.

Martii pushed a commit to Martii/OpenUserJS.org that referenced this pull request May 29, 2015
* Continue to use parallel *async* to retrieve info via git abstract
* New dep of *git-rev* to abstract a little direct `exec` is also available
* Bump *node* engine to latest 0.12.4

Closes OpenUserJS#426 and post dependency of OpenUserJS#635 after merge.
@Martii
Copy link
Member

Martii commented May 29, 2015

+1

Martii pushed a commit to Martii/OpenUserJS.org that referenced this pull request May 29, 2015
* Remove *jitsu* reference as soon to be obsolete with OpenUserJS#635

Applies to OpenUserJS#636 and OpenUserJS#426
Martii added a commit that referenced this pull request May 30, 2015
Nodejitsu shutting down. Modifications for new host.

Auto-merge
@Martii Martii merged commit 2096d0d into master May 30, 2015
@Martii Martii deleted the DOd branch May 30, 2015 06:57
@Martii Martii added migration Use this to indicate that it may apply to an existing or announced migration. CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. and removed BLOCKING Concentrate on bug fixes primarily. PR READY This is used to indicate that a pull request (PR) is ready for evaluation. labels May 30, 2015
@Martii
Copy link
Member

Martii commented May 30, 2015

note not all logs are showing this change and may be configured/initialized elsewhere... might need a restart of the server instead of a restart of the project.

A server reboot fixed a log clock however reboot also killed the web service... messaged @sizzlemctwizzle to restart ... apologies for the downtime. (everything was working until I rebooted... growing pangs :)

@sizzlemctwizzle
Copy link
Member Author

Back up again.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CODE Some other Code related issue and it should clearly describe what it is affecting in a comment. migration Use this to indicate that it may apply to an existing or announced migration.
Development

Successfully merging this pull request may close these issues.

2 participants