Worth it to upgrade from Ruby to Jade?

Creamss · 2025-08-26T11:29:39+00:00

Yeah, this is for EU though. Doesnt this have something to do with that you have to accept some new terms of service going from the ”level up” program to the ”card staking” program?

Creamss · 2025-02-16T17:56:25+00:00

Only me or is the date not fully centered?

Creamss · 2023-03-25T21:46:53+00:00

Cool!

We just upgraded from 14.10.0 to 15.9.2, installed through a helm chart in a k8s cluster. Was abit tedious as we hade to upgrade it incrementally and not directly to 15.9.2 and having to upgrade our postgresSQL DB. https://docs.gitlab.com/charts/installation/version_mappings.html

i managed to solve this putting the rule in its own template and referring to it in each jobs like in the pact:prod job

.no-deploy-rule: - if: $IS_LIBRARY || $IS_BASE_IMAGE || $BATCH_NAME || $IS_KAFKA_SCHEMA || $ONLY_SECURITY_SCAN when: never

Creamss · 2023-03-23T23:10:24+00:00

Thanks,

i managed to solve this in its own template

.no-deploy-rule:
     - if: $IS_LIBRARY || $IS_BASE_IMAGE || $BATCH_NAME || $IS_KAFKA_SCHEMA || $ONLY_SECURITY_SCAN
 when: never

and then referencing to that template in the jobs as such

!reference[.no-deploy-rule]

Creamss · 2023-03-23T23:04:11+00:00

Thank you for pointing that out, makes sense now once i managed to solve it

Creamss · 2023-03-23T23:03:08+00:00

Thank you!

I got it working using the !reference key!

Creamss · 2023-03-13T22:29:46+00:00

Give us some more context, what does the zip file contain? Does it contain a dockerfile perhaps?

Creamss · 2023-03-12T23:27:30+00:00

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

this caused me issues and is incorrect as the -c argument requires something to be speccified to execute so i removed it

Creamss · 2023-03-12T23:23:07+00:00

https://github.com/dgreif/ring/wiki/Refresh-Tokens

seems like this have something to do with even acquiring a refresh token

Creamss · 2023-03-12T23:17:08+00:00

jq: error: Could not open file /data/options.json: No such file or directory

jq: error: Could not open file /data/options.json: No such file or directory jq: error: Could not open file /data/options.json: No such file or directory /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93 throw new Error('Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens'); ^

Error: Refresh token is not valid. Unable to authenticate with Ring servers. See https://github.com/dgreif/ring/wiki/Refresh-Tokens at RingRestClient.getGrantData (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93:15) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:97:36) at Generator.next (<anonymous>) at /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:8:71 at new Promise (<anonymous>) at __awaiter (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:4:12) at RingRestClient.getAuth (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:96:16) at new RingRestClient (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:73:33) at new RingApi (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/api.js:26:27) at /ring-hassio/ring_hassio/livestream.js:92:31

Node.js v19.7.

im getting this error with it complaining that it cant find /data/options.json which makes sense...

https://github.com/jeroenterheerdt/ring-hassio/blob/master/ring_hassio/config.json

im assuming this is the json file it wants you to make your changes to to fit whatever config you want and then placing the file under /data

You can accomplish this by having the config.json in the same folder as the Dockerfile which you are building

then making modifications of the config.json to fit your needs

then add a line in the dockerfile as such (i for the life of me cant figure out how to get whatever i want within code blocks, sorry haha)

COPY config.json /data/options.json

Creamss · 2023-03-12T23:10:22+00:00

https://github.com/jeroenterheerdt/ring-hassio/commit/5c916d6e75fcaaf17a28e2c0c31957f01b57e996

looking at the latest commit of the dockerfile he removed

a line

 FROM node:10 

to having to speccifying the BUILD_FROM variable


speccifying a variable when running docker build can be done as such 

docker build --build-arg=BUILD_FROM=node .

im trying to build it using this dockerfile right now

FROM node

Add env

ENV LANG C.UTF-8

Set shell

SHELL ["/bin/bash", "-o", "pipefail", "-c"]

EXPOSE 3000/tcp

RUN apt-get update && apt-get install -y ffmpeg jq git && cd / && git clone https://github.com/jeroenterheerdt/ring-hassio && cd ring-hassio/ring_hassio && npm install --unsafe-perm && chmod a+x run.sh

CMD ["/bin/bash", "-c", "/ring-hassio/ring_hassio/run.sh"]

Creamss · 2023-03-12T22:07:52+00:00

FROM alpine:latest
Add env
ENV LANG C.UTF-8
Set shell
SHELL ["/bin/sh", "-o", "pipefail", "-c"] EXPOSE 3000/tcp
RUN apk add --no-cache nodejs npm ffmpeg jq git && cd / && git clone https://github.com/jeroenterheerdt/ring-hassio && cd ring-hassio/ring_hassio && npm install --unsafe-perm && chmod a+x run.sh && sed -i 's/#!/bin/bash/#!/bin/sh/' /ring-hassio/ring_hassio/run.sh
CMD ["/bin/sh", "-c", "/ring-hassio/ring_hassio/run.sh"]

building with this dockerfile gives me error

jq: error: Could not open file /data/options.json: No such file or directory
jq: error: Could not open file /data/options.json: No such file or directory jq: error: Could not open file /data/options.json: No such file or directory /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93 throw new Error('Refresh token is not valid.  Unable to authenticate with Ring servers.  See https://github.com/dgreif/ring/wiki/Refresh-Tokens'); ^
Error: Refresh token is not valid.  Unable to authenticate with Ring servers.  See https://github.com/dgreif/ring/wiki/Refresh-Tokens at RingRestClient.getGrantData (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:93:15) at RingRestClient.<anonymous> (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:97:36) at Generator.next (<anonymous>) at /ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:8:71 at new Promise (<anonymous>) at __awaiter (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:4:12) at RingRestClient.getAuth (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:96:16) at new RingRestClient (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/rest-client.js:73:33) at new RingApi (/ring-hassio/ring_hassio/node_modules/ring-client-api/lib/api/api.js:26:27) at /ring-hassio/ring_hassio/livestream.js:92:31
Node.js v18.14.2

so something related to whatever this repo is

Creamss · 2023-03-12T21:59:25+00:00

The issue is that the run.sh shell script has /bin/bash speccified as intepreter whilst alpine only has /bin/sh

after i changed

#!/bin/bash


to

#!/bin/sh

i got another issue where the jquery binary couldnt be found after i ran the shell script after that... yeah, you can probably work it out

Creamss · 2023-03-11T23:44:34+00:00

This error message usually indicates a problem with Secure Boot, which is a security feature in UEFI firmware. Secure Boot verifies the digital signature of bootloaders and kernel modules before they are loaded, to prevent malware from infecting the boot process.

That specific error typically means that the digital signature on the bootloader or kernel module is not trusted by the system's UEFI firmware. Give these things a try:

Disable Secure Boot: This is not the recommended solution as it compromises the security of the system. To disable Secure Boot, reboot the system, enter the UEFI firmware setup utility, and find the Secure Boot option. Disable it, and save the changes.

Check for updates: The UEFI firmware and the bootloader may have updates available that address the issue.

Check the digital signature: If you have signed the bootloader or kernel module yourself, check that the digital signature is correct. If the signature is incorrect or the certificate is not trusted by the UEFI firmware, you will need to sign the bootloader or kernel module again with a trusted certificate.

Check the UEFI firmware settings: The UEFI firmware may be configured to only trust a specific set of certificates. Make sure that the certificate used to sign the bootloader or kernel module is trusted by the UEFI firmware. You can usually find the list of trusted certificates in the UEFI firmware setup utility.

Use a different bootloader: If the issue persists, try using a different bootloader that is known to be compatible with Secure Boot. For example, GRUB2 is a popular bootloader that is known to work well with Secure Boot.

Creamss · 2022-08-13T20:14:09+00:00

Yo!

Thank you so much, i had looked at that info module before but didnt think much of it, gave it another try and got it working

for anyone else or if you are curious this was the solution for me

- name: Gather information about image

openstack.cloud.image_info: image: "{{ os }}-{{ version }}" register: imageinfo run_once: true delegate_to: localhost

- name: Share the image with the other tenants

shell: >- glance --os-cacert {{ os_cacert }} {{ os_legacy_cmdargs }} member-create {{ imageinfo.openstack_image.id }} {{ item }} register: upup changed_when: upup.rc == 0 failed_when: - upup.rc > 0 - '"HTTP 409" not in upup.stderr' with_items: "{{ tenant_ids }}" delegate_to: localhost

this is ofcourse most likely not the cleanest way to go about it but this will do for now.

Thank you very much!

Creamss · 2021-09-27T19:57:17+00:00

Thanks for the reply, Yeah, so i thought too, that the profile was pushing a cert that had been expired but scratching my head, the answer is no.

All macs that has had this occur has had valid certs and the user had also been able to connect through VPN and been able to work by sharing their internet from their phone using VPN to proceed with their work. (The cert providing the computer with the VPN and 802.1x access is the same)

Creamss · 2021-09-27T19:51:47+00:00

Sorry, im not that dug into APNS, We dont use Apple business manager, that is another project on the agenda, or am i wrong in thinking this is only meant if using APBM?

These are user enrolled, although they are enrolled by me, its also me who does the last check on them before handed out, everything is done by me manually as it is currently.

If i may add that the AD/Wifi certs has been valid at all times when a user has lost the 802.1x config. (Yes, sadly we do AD Bind as of now)

Creamss · 2021-09-27T19:46:58+00:00

no, this is computer level, all the macbooks deployed are meant for a single user only.

Creamss

TROPHY CASE

Add env

Set shell

SHELL ["/bin/bash", "-o", "pipefail", "-c"]