coala / devops Goto Github PK

Add a file named ISSUE_TEMPLATE.md which includes general information and guidelines for issue reporter, you can see ISSUE_TEMPLATE.md of coala repository for reference.
label: initiatives/gci
Opened by @Monal5031 at gitter//Monal5031

Which leads to content overflowing in mobile.

Solution: Use vw units.

Currently, the "page" for the list of short links is the coala.io configuration file. It would be pretty neat to have a better looking page for this. The main problem for creating something like this is over-complicating it (like for example, using PHP to generate it would result having a full PHP fpm setup).

@Nosferatul blog didn't show up on blog.coala.io due to an invalid url is set.
https://github.com/coala/devops/blob/master/venus/planet/planet.ini#L82
It should point to an RSS feed, this can be done simply /feed/ at the end.

Mailman is an attempt to get proper mailing lists in coala. Due to inexperience in handling mailman, it's better to abandon it and use services like Google Groups until an actual reason for the need of our own mailing list or someone who's experienced in handling mailman can help us maintain it.

difficulty/newcomer

I'm personally lazy have to pull changes and restart containers manually. This is a nice addition to make the work a bit more efficient.

Opened via gitter by @yukiisbored

Currently the web page for solar.coala.io is a plain old html file. It'll be nice to have the same styles as the new website. I'm thinking about having it as a portal for the various services we provide.

Opened via gitter by @yukiisbored

There is link to everyone's blog at the end.
Link to my blog seems to be the link of the RSS feed and not https://meetmangukiya.github.io

difficulty/hard

coala is needed to test if the config files are using the proper guidelines and CI is needed to enforce coala.

For some reason the icons aren't showing up.

Ref: coala/corobo#156

Due to time constraints, we often forgot to pull the changes from remote and update the containers. It'll be nice to have rultor or a similar tool that pulls and updates automatically

Opened via gitter by @yukiisbored

corobo is deprecating cobot. It should be abandon especially due to it's CPU utilization habits and excessive use of memory.

Of course, this will be done when corobo is mature. Right now, corobo still have some bugs that needs to be fixed.

short URL: www.coala.io/languages should redirect to https://coala.io/#/languages, but it is redirecting to
https://coala.io/#/home

The mumble server is hardly used and I think it's better to abadon it.

Running as root inside a container is as bad as running root on host. Since containers on Linux isn't as fully isolated as Jails on FreeBSD. It's honestly a really good idea to make sure none of these are running as root.

Venus cronjob is broken, most likely due to it not having an executable flag.

Opened via gitter by @yukiisbored

right now the only shortURL that works
is this one ---> coala.io/cep5

all the othere; i.e. coala.io/cep#

where # is 0 to 4 or 6 are re-directed to cEP-0000

From coala/cEPs#65

Some of our GSoC students uses Emojis on their blog posts, it'll be a good idea to have good emoji support with twemoji.

What do you mean by emoji support?

Not a lot of browsers/operating system can show emoji properly and they end up being tofu or black and white emoji if you have good fonts like Noto.

@yukiisbored here is the script that you'd have to run.
It will need:

• cobot gitter token
• cobot github token

You can just join one user by using it like this python3 join_coalaians.py --user <username>

I'd prefer that you make SEND_MESSAGE True which will send a message to all the people with whom cobot will join rooms that cobot is accessible on private chats from now on...
NOTE 1: ^^ If you run the script again, then it'll send the message again to that person, so if possible allow script to run completely, on all members.

NOTE 2: Please have a look at the logs once and join rooms with users that were not able to join with python3 join_coalaians.py --user <username>

NOTE 3: Please restart cobot after running this script

Thanks! cobot is accessible on Private chats as well, now! 🎉

Opened via gitter by @meetmangukiya

difficulty/newcomer
Opened by @jayvdb at Gitter

It'll be nice to have monitoring on the server level instead of external http checks like status.coala.io.
The reason for this is to see the status of the container, cpu and ram usage, etc.

Possible choices:

• Grafana-Prometheus
• Elastic-Kibana-Logstash
• Graylog

Opened via gitter by @yukiisbored

difficulty/low

solar.coala.io purely run docker containers now and it's preferable to move to a lightweight Linux distribution that's made only to run docker.
Opened by @yukiisbored at gitter/coala/devops

Opened via gitter by @yukiisbored

The images used should be frozen on a version, not directly use latest. This makes it reproducible and won't have a bug due to "a new update changed the function of X"

Opened via gitter by @yukiisbored

1. Review and merge #69
2. Update the secrets file to add new environment var ANSWER_END=http://0.0.0.0:8000
3. Update the compose file on the server

Healthcheck is a new-ish feature in Docker to check the actual status of the services/daemons of the container. Healthcheck can be implemented by having a "check command" like using curl to see if it returns 200 or not. It's preferable (for now) to add healthcheck on the compose file rather than the dockerfile.

Opened via gitter by @yukiisbored

Due to a pretty critical security issue, the landing image is modified with a Dockerfile. We should update the upstream image to prevent the "vendor" image from lagging behind it's development.

Hey, just noticed this, this is similar in nature but reason unknown, search endpoints are acting up again https://webservices.coala.io/search/bears?bear=RadonBear . Whereas other endpoints are working perfect. Docker compose setup in this repo is also working without any 500 server error at this endpoint.

StackOverflowGitterNotifier.jl for coala and coala-offtopic
This requires a cron setup.
For coala - tags are coala, right @jayvdb ?
For coala-offtopic - tags suggested are static-analysis, idioms, and zero

Opened via gitter by @meetmangukiya

Opened via gitter by @yukiisbored

Opened via gitter by @yukiisbored

The Wiki page should provide relevant information about the server, the config files, etc.

It should contain:

• The purpose of this repository
• Technical specifications for solar.coala.io
• Configuration style guidelines
• Information about the services

Grafana+Prometheus is pretty overkill for what we need. I think we should just move to a web log viewer that supports docker instead.

Add YAMLLintBear in .coafile and fix .yml file issues raised by coala. See coala/coala-bears#1799 for reference.
difficulty/newcomer

Opened via gitter by @Monal5031

Add a file named PULL_REQUEST_TEMPLATE.md which includes general information and guidelines for the author of Pull Request, you can see PULL_REQUEST_TEMPLATE.md of coala repository for reference.
label: initiatives/gci
Opened by @Monal5031 at gitter//Monal5031

Using volumes for configurations can be pretty bad. One of the problems is handling of permissions / ownership for the files, we want the containers to be properly contained and the files to be properly have the permissions/ownership it needs. Another reason for this is to have reproducible containers rather than having something that may change in the future uncontrollably.