Custom domains/hr

Miraheze može Wikijama dati prilagođene domene (npr. wiki.vašadomena.org) zahtjevom. Samo trebate pratiti sljedeće korake, i SSL potvrda za vašu wikiju (bez SSL potvrde nećete imati prilagođenu domenu - Ne prihvaćamo WoSign potvrdu. Ako želite koristiti [$LE Let's Encrypt], molimo recite u zadatku jer Let's Encrypt je proces kojim se baratmo bez intervencije/dodatnog rada od vas osim korištenja domene na našem poslužitelju):

Steps
Setting up a custom domain is as easy as following 4 steps:

1. Get a domain. To setup a custom domain, you will need to get a domain. There are many reputable registrars such as Namecheap where you can purchase a domain. Don't want to pay money for a domain? Click here for free domain services.

2. Point it to Miraheze. Once you have a domain, you'll need to point it to Miraheze. You can either point the namespace servers to Miraheze or set a CNAME record for the subdomain you want your wiki on pointing to mw-lb.miraheze.org. Promijenite imena poslužitelja "ns1.miraheze.org" i "ns2.miraheze.org" (ako ne znate kako to učiniti, obratite se registratoru domena); Dodajte CNAME na su-domenu (npr. "wiki."), i pošaljite to na "mw-lb.miraheze.org"; Ako koristite Cloudflare za DNS pslužitelj, posjetite Cloudflare stranicu da vidite kako to napraviti.

Each option has different pros and cons: Možda želite postaviti nameserver svoje domene na Miraheze. Imajte na umu da će bilo koje usluge koje se koriste s vašom domenom postati nedostupne i nećete moći kontrolirati domenu koju koristite.
 *  What should I choose? 
 * If you choose to simply point a subdomain to Miraheze, you'll have complete control of your DNS records but you'll need to manually set records yourself with your DNS provider.

3. Choose who will provide an SSL certificate. For your safety, Miraheze uses SSL/TLS to encrypt the connections from our servers to your browser to make sure no one intercepts your connection. For this reason, we need all custom domains to have an SSL certificate. You can either provide us your own SSL certificate or let us handle it completely (for free, via Let's Encrypt). Ako jest Let's Encrypt: Nemate ništa napraviti, uključujući obnavljanje, administrator sustava proći će kroz sve potrebne korake If you have choose your own SSL certificate: After you make your custom domain request, a system administrator who handles CSR requests will generate a CSR & private key (for use at our own servers), and the requested CSR will be emailed to you. You use this CSR to request your SSL certificate vendor to generate an SSL certificate with the CSR we gave you. You will need to email us the generated SSL certificate when this is done. If all of these steps are done, we will add the custom domain to your wiki, and we will notify you when this all is done. 4. Make the request!: Once you've done the steps above and have chosen who will provide the SSL certificate, make the request on Phabricator. In the form, all you need to do is provide your wiki's current subdomain, your desired domain, and whether or not you'll use Let's Encrypt (us handling the SSL) or if you'll provide an SSL certificate yourself. Custom domain request form (via Phabricator)

Treba li vam pomoć s ikojim korakom? Reception123 ili Paladox vam mogu pomoći.

Besplatne domene
Možete registrirati besplatnu poddomenu sa bilo kojom domenom koju želite (sve dok je imaju na web mjestu) umjesto domene Miraheze. Neke su domene vrlo kratke, tako da možete imati većinu punog imena domene za svoj wiki.

Dostupne stranice

URL structure
Miraheze is configured not to serve pages from the domain root. For example, if your wiki is  and its main page is called "Welcome", then the URL will not be   but instead   (note the   piece). Likewise, even if you use a custom domain, Miraheze will still serve pages with this URL structure. When users visit pages on the root (e.g. without the ), they'll be greeted by a page asking them if they meant to go to a page on the /wiki/ subdirectory and will provide them a link.

CloudFlare


CloudFlare users must turn off CloudFlare's DDoS/Origin IP protection system/workers. This is not negotiable. Popunite [$phabreq ovu anketu] na Phabricatoru za zahtjev CSR-a (ili direktno za potvrdu) Our IPs are already public so we do not need Origin IP protection, and we have DDoS protection through our network vendor.

Follow the steps to find out how to disable Cloudflare DDoS/Origin IP protection system (assuming you're using the dash.cloudflare.com dashboard).

Add  entry to. The cloud with an arrow must be grey. If it is yellow, click it to make it grey. Click "Add Record". The result have to look like the last image.
 * 1) Go to dash.cloudflare.com
 * 2) Click your domain in the dashboard.
 * 3) Go to "DNS".

If you are done with this, continue back on the steps above.

Please note that not following the rules above may result in your custom domain being removed immediately and further action being taken if necessary. In case of any doubt, feel free to contact us at sre@undefinedmiraheze.org or ask on the Phabricator task you create.

Tijelo za SSL certifikate
Miraheze prihvaća većinu ovlaštenja SSL certifikata koje prihvaćaju preglednici poput Mozilla Firefox. Kao što je gore spomenuto, više ne prihvaćamo WoSign certs.

Trenutačni autoritet koristi Miraheze prilagođene domene
Ispod je popis trenutnih ovlaštenja SSL certifikata koje koriste prilagođene domene. To ne znači da drugi koji nisu na ovom popisu nisu prihvaćeni.


 * Let's Encrypt - upravlja Miraheze, sve korake koji se tiču Let's Encrypt (osim postavljanja poslužitelja imena) vrši Miraheze Sysadmins
 * CloudFlare (Note: Additional restrictions apply. See section above for details.)
 * Comodo
 * Gandi
 * GeoTrust
 * GlobalSign
 * GoDaddy
 * RapidSSL