zydronium/getnamingo-registry
1
0
Fork 0
mirror of https://github.com/getnamingo/registry.git synced 2025-08-11 20:09:28 +02:00
Code Issues Projects Releases Packages Wiki Activity

1.0.16 preparation, further testing soon

Browse source
This commit is contained in:
Pinga 2025-02-19 10:45:45 +02:00
parent 9a962340b8
commit 9003766ef6
4 changed files with 59 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

40
README.md
View file

@ -87,41 +87,21 @@ After installation, be sure to review all the guides in the Documentation sectio
**Note for AWS/Google Cloud installations:** When installing on *AWS* or *Google Cloud*, ensure you provide the private/internal IPv4 address (e.g., `172.x.x.x` for AWS or `10.x.x.x` for Google Cloud) to the installer, rather than the public IPv4 address, as these platforms use private IPs for internal communication. For IPv6, you'll typically need to use the public IPv6 address for external-facing services. For most other cloud providers, such as DigitalOcean or Linode, you will generally need to provide the public IPv4 and public IPv6 addresses. **Note for AWS/Google Cloud installations:** When installing on *AWS* or *Google Cloud*, ensure you provide the private/internal IPv4 address (e.g., `172.x.x.x` for AWS or `10.x.x.x` for Google Cloud) to the installer, rather than the public IPv4 address, as these platforms use private IPs for internal communication. For IPv6, you'll typically need to use the public IPv6 address for external-facing services. For most other cloud providers, such as DigitalOcean or Linode, you will generally need to provide the public IPv4 and public IPv6 addresses.
### Update ### Updating
You must run update scripts in order, without skipping versions. For example, if you're on 1.0.13 and the latest is 1.0.15, first update to 1.0.14, then to 1.0.15. To update, you **must run the update scripts sequentially** without skipping versions.
For example, if you're on **v1.0.13** and the latest is **v1.0.15**, first update to **v1.0.14**, then to **v1.0.15**.
- v1.0.14 to v1.0.15 - backup registry, download and run the [update1015.sh](docs/update1015.sh) script. - **v1.0.15 → v1.0.16**
Download and run the [`update1016.sh`](docs/update1016.sh) script.
- v1.0.13 to v1.0.14 - backup registry, download and run the [update1014.sh](docs/update1014.sh) script. - **v1.0.14 → v1.0.15**
Download and run the [`update1015.sh`](docs/update1015.sh) script.
- v1.0.12 to v1.0.13 - backup registry, download and run the [update1013.sh](docs/update1013.sh) script. - **v1.0.13 → v1.0.14**
Download and run the [`update1014.sh`](docs/update1014.sh) script.
- v1.0.11 to v1.0.12 - backup registry, download and run the [update1012.sh](docs/update1012.sh) script. For **older versions**, please refer to [`update.md`](docs/update.md).
- v1.0.10 to v1.0.11 - backup registry, download and run the [update1011.sh](docs/update1011.sh) script.
- v1.0.9 to v1.0.10 - backup registry, download and run the [update1010.sh](docs/update1010.sh) script.
- v1.0.8 to v1.0.9 - backup registry, download and run the [update109.sh](docs/update109.sh) script.
- v1.0.7 to v1.0.8 - backup registry, download and run the [update108.sh](docs/update108.sh) script.
- v1.0.6 to v1.0.7 - backup registry, download and run the [update107.sh](docs/update107.sh) script.
- v1.0.5 to v1.0.6 - backup registry, download and run the [update106.sh](docs/update106.sh) script.
- v1.0.4 to v1.0.5 - backup registry, download and run the [update105.sh](docs/update105.sh) script.
- v1.0.3 to v1.0.4 - backup registry, download and run the [update104.sh](docs/update104.sh) script.
- v1.0.2 to v1.0.3 - backup registry, download and run the [update103.sh](docs/update103.sh) script.
- v1.0.1 to v1.0.2 - backup registry, download and run the [update102.sh](docs/update102.sh) script.
- v1.0.0 to v1.0.1 - backup registry, download and run the [update101.sh](docs/update101.sh) script.
- v1.0.0-RC4 to v1.0.0 - backup registry, refer to [upgrade.md](docs/upgrade.md).
### [Configuration Guide](docs/configuration.md) ### [Configuration Guide](docs/configuration.md)

2
cp/resources/views/partials/footer.twig
View file

@ -14,7 +14,7 @@
<a href="https://namingo.org" target="_blank" class="link-secondary" rel="noopener">Namingo</a> <a href="https://namingo.org" target="_blank" class="link-secondary" rel="noopener">Namingo</a>
</li> </li>
<li class="list-inline-item"> <li class="list-inline-item">
v1.0.16-a v1.0.16
</li> </li>
</ul> </ul>
</div> </div>

2
docs/install.sh
View file

@ -246,7 +246,7 @@ EOF
wget "http://www.adminer.org/latest.php" -O /usr/share/adminer/latest.php wget "http://www.adminer.org/latest.php" -O /usr/share/adminer/latest.php
ln -s /usr/share/adminer/latest.php /usr/share/adminer/adminer.php ln -s /usr/share/adminer/latest.php /usr/share/adminer/adminer.php
git clone --branch v1.0.15 --single-branch https://github.com/getnamingo/registry /opt/registry git clone --branch v1.0.16 --single-branch https://github.com/getnamingo/registry /opt/registry
mkdir -p /var/log/namingo mkdir -p /var/log/namingo
chown -R www-data:www-data /var/log/namingo chown -R www-data:www-data /var/log/namingo

66
docs/upgrade.md → docs/update.md
View file

@ -1,11 +1,41 @@
# Namingo Upgrade Guide (from v1.0.0-RC4 or later) # Namingo Update Guide
## Introduction ## v1.0.0 to v1.0.13
This guide will walk you through the steps to upgrade your registry system. The process involves backing up your current setup, cloning the latest code, making database changes, and updating configuration files. You must run update scripts in order, without skipping versions. For example, if you're on 1.0.10 and the latest is 1.0.12, first update to 1.0.11, then to 1.0.12.
**This upgrade guide is a work in progress, and some instructions might be generic or unclear, so please tune them for your specific situation.**
## Step 1: Backup Your Current Setup - v1.0.12 to v1.0.13 - download and run the [update1013.sh](docs/update1013.sh) script.
- v1.0.11 to v1.0.12 - download and run the [update1012.sh](docs/update1012.sh) script.
- v1.0.10 to v1.0.11 - download and run the [update1011.sh](docs/update1011.sh) script.
- v1.0.9 to v1.0.10 - download and run the [update1010.sh](docs/update1010.sh) script.
- v1.0.8 to v1.0.9 - download and run the [update109.sh](docs/update109.sh) script.
- v1.0.7 to v1.0.8 - download and run the [update108.sh](docs/update108.sh) script.
- v1.0.6 to v1.0.7 - download and run the [update107.sh](docs/update107.sh) script.
- v1.0.5 to v1.0.6 - download and run the [update106.sh](docs/update106.sh) script.
- v1.0.4 to v1.0.5 - download and run the [update105.sh](docs/update105.sh) script.
- v1.0.3 to v1.0.4 - download and run the [update104.sh](docs/update104.sh) script.
- v1.0.2 to v1.0.3 - download and run the [update103.sh](docs/update103.sh) script.
- v1.0.1 to v1.0.2 - download and run the [update102.sh](docs/update102.sh) script.
- v1.0.0 to v1.0.1 - download and run the [update101.sh](docs/update101.sh) script.
## v1.0.0-RC4 to v1.0.0
This guide will walk you through the steps to update your registry system. The process involves backing up your current setup, cloning the latest code, making database changes, and updating configuration files.
**This update guide is a work in progress, and some instructions might be generic or unclear, so please tune them for your specific situation.**
### Step 1: Backup Your Current Setup
1. Backup Web and Registry Directories: 1. Backup Web and Registry Directories:
@ -20,15 +50,15 @@ cp -r /opt/registry /opt/registry_backup
mysqldump -u your_username -p your_database_name > database_backup.sql mysqldump -u your_username -p your_database_name > database_backup.sql
``` ```
## Step 2: Clone the Latest Code ### Step 2: Clone the Latest Code
1. Clone the Repository: 1. Clone the Repository:
```bash ```bash
git clone https://github.com/getnamingo/registry /opt/upgrade git clone https://github.com/getnamingo/registry /opt/update
``` ```
## Step 3a: Make Database Changes (from v1.0.0-RC4) ### Step 3a: Make Database Changes (from v1.0.0-RC4)
1. Access MySQL Terminal: 1. Access MySQL Terminal:
@ -48,7 +78,7 @@ ADD COLUMN `companyNumber` varchar(30) DEFAULT NULL BEFORE `vatNumber`;
UPDATE settings SET value = NULL WHERE name = 'launch_phases'; UPDATE settings SET value = NULL WHERE name = 'launch_phases';
``` ```
## Step 3b: Make Database Changes (from v1.0.0-RC5) ### Step 3b: Make Database Changes (from v1.0.0-RC5)
1. Access MySQL Terminal: 1. Access MySQL Terminal:
@ -78,7 +108,7 @@ DROP INDEX `tldid`;
**Warning: If you have already activated the database audit feature, you will need to update the respective audit table to reflect these changes as well.** **Warning: If you have already activated the database audit feature, you will need to update the respective audit table to reflect these changes as well.**
## Step 4: Update Configuration Files ### Step 4: Update Configuration Files
1. Add `minimum_data` Setting in `config.php`/`.env` Files: 1. Add `minimum_data` Setting in `config.php`/`.env` Files:
Open your configuration files and add the following setting: Open your configuration files and add the following setting:
@ -103,19 +133,19 @@ ZONE_MODE=nice // or default based on your requirement
3. Change records `whois_ipv4`/`whois_ipv6`/`epp_host_ipv6`/`das_ipv4`/`das_ipv6` in `config.php` Files for WHOIS/DAS/EPP components to match the new version. 3. Change records `whois_ipv4`/`whois_ipv6`/`epp_host_ipv6`/`das_ipv4`/`das_ipv6` in `config.php` Files for WHOIS/DAS/EPP components to match the new version.
## Step 5: Replace Old Files with New Files ### Step 5: Replace Old Files with New Files
1. Make sure to preserve the old `.env` and `config.php` files. 1. Make sure to preserve the old `.env` and `config.php` files.
2. Replace Files in `/opt/registry` and `/var/www`: 2. Replace Files in `/opt/registry` and `/var/www`:
```bash ```bash
cp -r /opt/upgrade/* /opt/registry/ cp -r /opt/update/* /opt/registry/
cp -r /opt/upgrade/cp/* /var/www/ cp -r /opt/update/cp/* /var/www/
cp -r /opt/upgrade/whois/* /var/www/ cp -r /opt/update/whois/* /var/www/
``` ```
## Step 6: Delete Panel Cache and Update Composer ### Step 6: Delete Panel Cache and Update Composer
1. Delete All Folders in `/var/www/cp/cache`: 1. Delete All Folders in `/var/www/cp/cache`:
@ -134,7 +164,7 @@ find /var/www/cp/cache/* -type d -exec rm -rf {} +
/var/www/whois /var/www/whois
``` ```
## Step 7: Restart Services ### Step 7: Restart Services
```bash ```bash
systemctl restart caddy systemctl restart caddy
@ -143,7 +173,3 @@ systemctl restart whois
systemctl restart rdap systemctl restart rdap
systemctl restart das systemctl restart das
``` ```
## Conclusion
Following these steps will ensure that your registry system is upgraded successfully. If you encounter any issues, please refer to the documentation or contact support for assistance.