linkedin / linkedin/oncall

Need clear instructions on installing from scratch

Open
#175 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.3k
Forks
245
PR merge metrics
No merged PRs in 30d

Description

Hi,

I'm having trouble installing oncall in our linux environment using the instructions given.

Here is one of the errors while running **"python setup.py develop"** :
I have a venv set up with python 3.6.3

`
Processing dependencies for oncall==1.1.0
Searching for slackclient
Reading https://pypi.python.org/simple/slackclient/
Downloading https://files.pythonhosted.org/packages/1f/9e/dd5bb327786be753e5d8de976082eb714cb83abeb00f67f0646ba2e166ad/slackclient-1.2.1.tar.gz#sha256=e9de0c893e8c5473107f5927ae1e543d35246f0c834f5e86470b22b762211577
error: Download error for https://files.pythonhosted.org/packages/1f/9e/dd5bb327786be753e5d8de976082eb714cb83abeb00f67f0646ba2e166ad/slackclient-1.2.1.tar.gz#sha256=e9de0c893e8c5473107f5927ae1e543d35246f0c834f5e86470b22b762211577: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)
`

1) Can we have clear step by step instructions to download and install oncall for both development and separately for production use ? Please note that not everyone uses Docker.

2) Is it possible to package oncall so we can start it easily ? i.e. minimum run. For example in a VM or as a single zip file ?

Thanks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with setup.py and the current installation instructions, including the Docker guidance, to identify the development and production paths described by the issue. Document reproducible Linux installation steps and clarify whether a simpler VM or archive-based packaging path is supported; done means both use cases have clear instructions and the packaging request has an explicit outcome.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.