zydronium/getnamingo-registry
1
0
Fork 0
mirror of https://github.com/getnamingo/registry.git synced 2025-07-11 21:38:12 +02:00
Code Issues Projects Releases Packages Wiki Activity

Update install.md

Browse source
This commit is contained in:
Pinga 2025-07-07 12:51:20 +03:00
parent d068935d69
commit 3cf4d43f03
1 changed files with 23 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

24
docs/install.md
View file

@ -1,9 +1,31 @@
# Namingo Registry: Manual Installation Guide
> **⚠️ This manual installation guide for the Namingo domain registry platform is provided for reference and debugging purposes only. It is no longer supported. For all new installations, please use the automated installer available at [https://namingo.org](https://namingo.org) for a faster and more reliable setup.**
> **⚠️ This manual installation guide for the Namingo domain registry platform is intended for advanced use cases or situations where the automated installer is not suitable or fails. For standard setups, please use the official installer at [https://namingo.org](https://namingo.org) for a faster and more reliable experience.**
After completing the installation, please refer to the [Configuration Guide](configuration.md) to tailor the system to your specific requirements. Once configured, visit the [Initial Operation Guide](iog.md) for detailed instructions on how to set up your registry, add registrars, and perform other essential operational tasks. To upgrade from older versions, please see our [upgrade guide](upgrade.md).
## Notes
### Systems with Partial or Misconfigured IPv6 Support
If your system has partial or broken IPv6 (e.g., `ping -6 ipv6.google.com` fails), edit `/etc/gai.conf` and add or uncomment the following line:
```bash
precedence ::ffff:0:0/96 100
```
This ensures IPv4 is preferred when IPv6 is broken.
In the `config.php` files for WHOIS or DAS, replace `::` with `false`, or use `0.0.0.0` for EPP.
---
### AWS / Google Cloud Installations
When installing on AWS or Google Cloud:
- Use the **internal/private IPv4** address (e.g., `172.x.x.x` for AWS or `10.x.x.x` for Google Cloud) during setup — these platforms route traffic internally via private IPs.
- Use the **public IPv6** address for external-facing services.
For most other providers like **DigitalOcean** or **Linode**, you should provide the **public IPv4 and public IPv6** addresses directly.
## 1. Install the required packages:
```bash