This issue is a kind reminder that your repository has been inactive for 185 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

Please check for some "if (ios)" logic in the app. I suspect it only shows the deep link URL if on iOS, which is not helpful as it should work on Android as well.

@esune

In order to decommission the demo, we need to complete the following steps:

• remove "Conference Book" references from public-facing the BC Digital Trust website (@alexgmetcalf )
• back-up the wallet (@WadeBarnes / @esune )
• spin down the deployments (@WadeBarnes / @esune )
• remove configurations from OCP (@WadeBarnes / @esune / @rajpalc7 )
• close this issue (@WadeBarnes / @esune )
• archive this repository (@WadeBarnes / @esune )

This issue is a kind reminder that your repository has been inactive for 180 days. Some repositories are maintained in accordance with business requirements that infrequently change thus appearing inactive, and some repositories are inactive because they are unmaintained.

To help differentiate products that are unmaintained from products that do not require frequent maintenance, repomountie will open an issue whenever a repository has not been updated in 180 days.

• If this product is being actively maintained, please close this issue.
• If this repository isn't being actively maintained anymore, please archive this repository. Also, for bonus points, please add a dormant or retired life cycle badge.

Thank you for your help ensuring effective governance of our open-source ecosystem!

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means its critical that we work to make our content as discoverable as possible; Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's in, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.

iiw-book services should be deployed in test, prod.

• test services are all-new and will need to be configured from scratch.
• prod services should have their wallets carried over from the devex-von-image-tools namespace so we can decommission the old ones. @wadeking98 please proceed with deploying the agent in read only mode, using the wallet and secret values from OCP3. Once ready, coordinate with @WadeBarnes to add the vonx.io routes and certificates, and switch the DNS entry to point to the new cluster.

No Project Lifecycle Badge found in your readme!

Hello! I scanned your readme and could not find a project lifecycle badge. A project lifecycle badge will provide contributors to your project as well as other stakeholders (platform services, executive) insight into the lifecycle of your repository.

What is a Project Lifecycle Badge?

It is a simple image that neatly describes your project's stage in its lifecycle. More information can be found in the project lifecycle badges documentation.

What do I need to do?

I suggest you make a PR into your README.md and add a project lifecycle badge near the top where it is easy for your users to pick it up :). Once it is merged feel free to close this issue. I will not open up a new one :)

Update genesis configmap in https://github.com/bcgov/iiwbook/blob/master/openshift/templates/iiw-book-agent/iiw-book-agent-deploy.yaml to point to http://test.bcovrin.vonx.io/

I am running this in Local Machine using Docker but port 7070 fails to start
Everything else runs well

Here is additional error on trail

iiw-book-service_1   | Traceback (most recent call last):
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connection.py", line 159, in _new_conn
iiw-book-service_1   |     (self._dns_host, self.port), self.timeout, **extra_kw)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/util/connection.py", line 80, in create_connection
iiw-book-service_1   |     raise err
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/util/connection.py", line 70, in create_connection
iiw-book-service_1   |     sock.connect(sa)
iiw-book-service_1   | ConnectionRefusedError: [Errno 111] Connection refused
iiw-book-service_1   | 
iiw-book-service_1   | During handling of the above exception, another exception occurred:
iiw-book-service_1   | 
iiw-book-service_1   | Traceback (most recent call last):
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connectionpool.py", line 600, in urlopen
iiw-book-service_1   |     chunked=chunked)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connectionpool.py", line 354, in _make_request
iiw-book-service_1   |     conn.request(method, url, **httplib_request_kw)
iiw-book-service_1   |   File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1254, in request
iiw-book-service_1   |     self._send_request(method, url, body, headers, encode_chunked)
iiw-book-service_1   |   File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1300, in _send_request
iiw-book-service_1   |     self.endheaders(body, encode_chunked=encode_chunked)
iiw-book-service_1   |   File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1249, in endheaders
iiw-book-service_1   |     self._send_output(message_body, encode_chunked=encode_chunked)
iiw-book-service_1   |   File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 1036, in _send_output
iiw-book-service_1   |     self.send(msg)
iiw-book-service_1   |   File "/opt/rh/rh-python36/root/usr/lib64/python3.6/http/client.py", line 974, in send
iiw-book-service_1   |     self.connect()
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connection.py", line 181, in connect
iiw-book-service_1   |     conn = self._new_conn()
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connection.py", line 168, in _new_conn
iiw-book-service_1   |     self, "Failed to establish a new connection: %s" % e)
iiw-book-service_1   | urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f7a2df0fd30>: Failed to establish a new connection: [Errno 111] Connection refused
iiw-book-service_1   | 
iiw-book-service_1   | During handling of the above exception, another exception occurred:
iiw-book-service_1   | 
iiw-book-service_1   | Traceback (most recent call last):
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/adapters.py", line 449, in send
iiw-book-service_1   |     timeout=timeout
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/connectionpool.py", line 638, in urlopen
iiw-book-service_1   |     _stacktrace=sys.exc_info()[2])
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/urllib3/util/retry.py", line 398, in increment
iiw-book-service_1   |     raise MaxRetryError(_pool, url, error or ResponseError(cause))
iiw-book-service_1   | urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='iiw-book-agent', port=4000): Max retries exceeded with url: /schemas (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7a2df0fd30>: Failed to establish a new connection: [Errno 111] Connection refused',))
iiw-book-service_1   | 
iiw-book-service_1   | During handling of the above exception, another exception occurred:
iiw-book-service_1   | 
iiw-book-service_1   | Traceback (most recent call last):
iiw-book-service_1   |   File "./manage.py", line 21, in <module>
iiw-book-service_1   |     main()
iiw-book-service_1   |   File "./manage.py", line 17, in main
iiw-book-service_1   |     execute_from_command_line(sys.argv)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
iiw-book-service_1   |     utility.execute()
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/django/core/management/__init__.py", line 357, in execute
iiw-book-service_1   |     django.setup()
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
iiw-book-service_1   |     apps.populate(settings.INSTALLED_APPS)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/django/apps/registry.py", line 122, in populate
iiw-book-service_1   |     app_config.ready()
iiw-book-service_1   |   File "/opt/app-root/src/iiw_book/apps.py", line 31, in ready
iiw-book-service_1   |     schema_response = requests.post(f"{AGENT_URL}/schemas", json=schema_body)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/api.py", line 116, in post
iiw-book-service_1   |     return request('post', url, data=data, json=json, **kwargs)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/api.py", line 60, in request
iiw-book-service_1   |     return session.request(method=method, url=url, **kwargs)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/sessions.py", line 533, in request
iiw-book-service_1   |     resp = self.send(prep, **send_kwargs)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/sessions.py", line 646, in send
iiw-book-service_1   |     r = adapter.send(request, **kwargs)
iiw-book-service_1   |   File "/opt/app-root/lib/python3.6/site-packages/requests/adapters.py", line 516, in send
iiw-book-service_1   |     raise ConnectionError(e, request=request)
iiw-book-service_1   | requests.exceptions.ConnectionError: HTTPConnectionPool(host='iiw-book-agent', port=4000): Max retries exceeded with url: /schemas (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7a2df0fd30>: Failed to establish a new connection: [Errno 111] Connection refused',))

TL;DR

Topics greatly improve the discoverability of repos; please add the short code from the table below to the topics of your repo so that ministries can use GitHub's search to find out what repos belong to them and other visitors can find useful content (and reuse it!).

Why Topic

In short order we'll add our 800th repo. This large number clearly demonstrates the success of using GitHub and our Open Source initiative. This huge success means it's critical that we work to make our content as discoverable as possible. Through discoverability, we promote code reuse across a large decentralized organization like the Government of British Columbia as well as allow ministries to find the repos they own.

What to do

Below is a table of abbreviation a.k.a short codes for each ministry; they're the ones used in all @gov.bc.ca email addresses. Please add the short codes of the ministry or organization that "owns" this repo as a topic.

That's it, you're done!!!

How to use

Once topics are added, you can use them in GitHub's search. For example, enter something like org:bcgov topic:citz to find all the repos that belong to Citizens' Services. You can refine this search by adding key words specific to a subject you're interested in. To learn more about searching through repos check out GitHub's doc on searching.

Pro Tip 🤓

• If your org is not in the list below, or the table contains errors, please create an issue here.

• While you're doing this, add additional topics that would help someone searching for "something". These can be the language used javascript or R; something like opendata or data for data only repos; or any other key words that are useful.

• Add a meaningful description to your repo. This is hugely valuable to people looking through our repositories.

• If your application is live, add the production URL.

Ministry Short Codes

NOTE See an error or omission? Please create an issue here to get it remedied.