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

Hello & welcome to appcanary/coalmine! #361

Open
phillmv opened this issue Jun 5, 2018 · 2 comments
Open

Hello & welcome to appcanary/coalmine! #361

phillmv opened this issue Jun 5, 2018 · 2 comments

Comments

@phillmv
Copy link
Member

phillmv commented Jun 5, 2018

Hi everyone on @appcanary/customers! In lieu of sharing everyone's emails with each other, I went ahead and created a team.

Thanks for taking an interest in this project.

Here are some tasks that come to mind:

  • getting this deployable in a docker environment
  • identifying out any secrets we may have left behind
  • swapping out any services that are not necessary as an open source project (i.e. Stripe, Google Analytics, Intercom, etc)

Once a couple people have a handle on what's going on, we can open source it.

I'm be happy to get on a call and talk thru the code base with anyone who wants to listen.

Cheers,

@jdno
Copy link
Contributor

jdno commented Jun 11, 2018

Hi @phillmv.

We here at Inspire are very interested in running the application ourselves, because we want to keep the server-side monitoring alive. I just set up the application locally, and am ready to go through it a bit and see what needs to be done.

There are a few process-oriented tasks that I would like to see in any open source project:

  • Protect the master branch and start requiring pull request reviews by maintainers
  • Adopt any versioning, start using releases (optional) and add a changelog
  • Adopt a Ruby style and configure Rubocop, once open sourced set up CodeClimate
  • Add badges to the README (just because)

Besides these more process-oriented tasks, I am interested to learn what functional changes need to happen to deploy the application. You mentioned third-party integrations for example. I saw that the API URL is hardcoded in the Agent, so that's something we need to change as well.

Maybe we can create some kind of roadmap and a detailed list of issues so that we can pick them up one by one and work through them.

Let me know what you think. I'd be happy to jump on a call to discuss the next steps.

Cheers,
Jan David

@phillmv
Copy link
Member Author

phillmv commented Jun 11, 2018

Protect the master branch and start requiring pull request reviews by maintainers

Turned on.

I am interested to learn what functional changes need to happen to deploy the application.

@krallin mentioned he could help dockerize it.

Otherwise, it's about ripping out integrations. For instance, you'll want to set up Sentry or replace it with exceptions-notifier.

I saw that the API URL is hardcoded in the Agent, so that's something we need to change as well.

You can configure it via debug mode iirc (run the agent with CANARY_ENV=debug as a bash var) but yeah. The trickiest part will be

a) getting the thing to compile since Go has moved on
b) ensuring continued access to the packages since we'll likely cease to pay packagecloud

I'd be happy to jump on a call to discuss the next steps.

I'd also be happy to do this with one more interested person :)

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