Alexander Ustyugov ulexxander

Extend Gitlab Access Tokens

Gitlab enforced token expiry limits to 365 days last year, and the time is now upon us.

They don't have an opt-out for this, and haven't provided a way to easily extend tokens in the web interface. They have also gated their credential management interface behind their Ultimate license.

This quickly thrown together script will allow you to add an extra year to all tokens that expire in the next 30 days. It will not reactivate tokens that have already expired.

Requires the python-gitlab module. Edit your self-hosted Gitlab instance details into the script and run it. It will dump out CSVs of all expiring tokens, and then dump out a list of commands you can paste into a gitlab-rails console session to extend the expiry date by another year. If you need them to be active for longer, change 1.year.from_now to the value of your choice, e.g. `10.years.fro

PHP Form submitting

If we have the following structure in our application:

📁 application_folder_name
- 📄 index.php
- 📄 handle_form.php
- 📄 main.js

And we fill our index.php with the following content just to get a basic website with a form working. You should be able to run this through a php-server of your choice.

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

There are always 24 hours in a day.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).

Check if User Exists

id -u "Username"

You can use it in a conditional:

	#!/bin/sh

	cat <<EOF >/tmp/adminer.conf
	server {

	listen 80;
	server_name localhost;

	index index.php;

	# This file is licensed under the terms of the MIT license https://opensource.org/license/mit
	# Copyright (c) 2021-2025 Marat Reymers

	## Golden config for golangci-lint v2.1.6
	#
	# This is the best config for golangci-lint based on my experience and opinion.
	# It is very strict, but not extremely strict.
	# Feel free to adapt it to suit your needs.
	# If this config helps you, please consider keeping a link to this file (see the next comment).

	#!/usr/bin/env bash

	# To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error
	# Make sure that the .gnupg directory and its contents is accessibile by your user.
	chown -R $(whoami) ~/.gnupg/

	# Also correct the permissions and access rights on the directory
	chmod 600 ~/.gnupg/*
	chmod 700 ~/.gnupg

	/* Shadow 0dp */
	box-shadow: none;

	/* Shadow 1dp */
	box-shadow: 0 1px 1px 0 rgba(0,0,0,0.14), 0 2px 1px -1px rgba(0,0,0,0.12), 0 1px 3px 0 rgba(0,0,0,0.20);

	/* Shadow 2dp */
	box-shadow: 0 2px 2px 0 rgba(0,0,0,0.14), 0 3px 1px -2px rgba(0,0,0,0.12), 0 1px 5px 0 rgba(0,0,0,0.20);

	/* Shadow 3dp */

	#!/bin/bash

	# Custom scripts here
	echo "This is an extended entrypoint!"

	# Run the original entrypoint located at
	# /docker-entrypoint.sh
	exec /docker-entrypoint.sh "$@"

	[
	{
	"name": "Afghanistan",
	"dial_code": "+93",
	"code": "AF"
	},
	{
	"name": "Aland Islands",
	"dial_code": "+358",
	"code": "AX"