Skip to content
This repository has been archived by the owner on Dec 11, 2021. It is now read-only.

Basic Environment Setup #8

Closed
wants to merge 1 commit into from

Conversation

geekman-rohit
Copy link
Contributor

Basic Environment Setup. Still working on better way to do the tests, but some reviews would help.

"important": true,
"outline-none": false,
"overqualified-elements": false,
"text-indent": false

Choose a reason for hiding this comment

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

The indentation in this file is wrong. Use tabs :)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The indentation looks wrong in all files! Though I had soft tabs turned off! fixing it now!!

Copy link

Choose a reason for hiding this comment

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

Sneaky little text editors.

@arthurvr
Copy link

Might want to setup some JavaScript code style linting as well? Maybe JSCS?

Let's not forget a .gitattributes file as well.

Do we also want to setup CI (using Travis) from the beginning? Seems like a good idea (even if it's just for linting)

@geekman-rohit
Copy link
Contributor Author

We certainly need another linting. Some of these mistakes should have been pointed out by linting test. I'll add JSCS

@@ -0,0 +1,10 @@
var express = require( "express" ),
app, server, config;

Choose a reason for hiding this comment

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

Use separate var for each of these.

Choose a reason for hiding this comment

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

Themeroller:port=5000
Themeroller:db_name=themeroller
Themeroller:db_user=root
Themeroller:db_password=
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This file shouldn't be here , I'l delete in next push

@sfrisk
Copy link

sfrisk commented Jul 7, 2015

Looks good to me right now, @arschmitz ?

@@ -0,0 +1,8 @@
language: node_js
node_js:
- "0.10"
Copy link

Choose a reason for hiding this comment

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

Should we test only on 0.10? We do run 0.10 in production, but testing in 0.12 also is going to save us pain when our production servers update.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll bring this up and all other issues in meeting today one by one, and then update the PR.


app.use ( "/", express.static( "./static" ) );
app.listen( port, function() {
console.log( "Listening on http://localhost:" + port );
Copy link

Choose a reason for hiding this comment

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

Should we hardcode localhost?

Choose a reason for hiding this comment

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

Yes, that's fine - its just a convenience when testing locally. If it turns out later I'm wrong about it, we can still fix it quickly enough...

@sfrisk
Copy link

sfrisk commented Jul 10, 2015

This PR has been updated. Please do a final review, and if everyone is satisfied, I'll pull it in.

<html lang="en">
<head>
<meta charset="utf-8">
<title>Themeroller</title>
Copy link

Choose a reason for hiding this comment

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

This is picky, but maybe say Chassis Themeroller for the title?

That's really my only feedback I have left on this. Tweak that and I'll pull this in.

Choose a reason for hiding this comment

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

Why did you pull this in already? That's a totally valid point and there's no hurry.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Umm @arthurvr , me and srisk had a conversation about that on IRC, I needed this environment PR for splitting things into two PRs UI and API and laying a base, that page will soon get replaced by UI page in next PR

Choose a reason for hiding this comment

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

That's no reason to land this already, you could just base those PRs on this branch and rebase it afterwards.

Copy link

Choose a reason for hiding this comment

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

@arthurvr, it was a minor thing, and since the page was going to be replaced, I decided it was okay if we just did the PR.

@sfrisk sfrisk closed this in 2d960d4 Jul 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants