A Technical Tutorial: Setting Up a Web Server for an Installation

A web server can turn an artwork into a responsive space: visitors might trigger sound, browse an archive, alter projected visuals or contribute data from a phone. For a gallery, festival or temporary exhibition, the server should be quiet, dependable and easy to restore when something goes wrong.

This guide covers a practical local-network setup for an interactive installation. It is suitable for a Raspberry Pi, mini PC or laptop, and it treats the server as part of the artwork’s infrastructure rather than as an afterthought. For inspiration, browse the experimental projects presented through the ITP 30 Show, where technology and creative practice meet in many forms.

Define The Installation’s Technical Shape

Start by mapping the experience. List every input, output and dependency: touchscreens, proximity sensors, projectors, speakers, cameras, MIDI devices, external APIs and stored media. Decide whether the work needs internet access or whether it can operate entirely on a private local area network.

A self-contained installation is usually safer. A server on the local network can deliver a web interface even when a venue’s Wi-Fi is congested or unavailable. If the work is touring between Sydney, Melbourne and regional venues, package all assets locally and avoid relying on a cloud service for the core interaction.

Choose hardware with enough capacity for the actual workload. A Raspberry Pi is suitable for lightweight HTML, JavaScript and sensor control, while video playback, computer vision or several high-resolution displays may require a small desktop computer. Include a reliable power supply, ventilation and a backup storage device.

Install A Lightweight Web Stack

For a Linux-based computer, install the operating system to a quality microSD card or solid-state drive, then update it before the exhibition. Assign the machine a clear hostname, such as gallery-server, and use a static local IP address or a DHCP reservation so connected devices can find it consistently.

A simple Python server is useful during prototyping:

python3 -m http.server 8000 --directory /home/pi/installation

For a more robust deployment, use Nginx or Caddy to serve the files and manage automatic restarts. Keep the project in a version-controlled folder, and store large videos or audio files on the local drive rather than inside a database. A small README should explain how to start, stop and reset the system.

Creative technology often benefits from reusing available equipment. The discussion of e-waste for art is a useful reminder that older screens, controllers and computers can gain a new purpose, provided their condition and security are assessed first.

Build The Local Network

Create a dedicated network using a venue-approved router. Give the server a predictable address, then connect tablets, phones, microcontrollers and display computers to the same network. Test both wired Ethernet and Wi-Fi, since a crowded exhibition floor can expose weaknesses that are invisible in a studio.

Avoid publishing the server directly to the public internet unless the project genuinely requires it. Disable unnecessary services, change default passwords and use a firewall. If visitors can submit text, images or personal information, collect as little as possible and explain its use. For an Australian venue, consider the Australian Privacy Principles and the organisation’s own data policy.

Network names and passwords should be documented for technicians but not displayed where visitors can see them. If the venue uses enterprise Wi-Fi, ask whether device-to-device traffic is blocked; some guest networks prevent connected devices from communicating with one another. A separate router can make the installation more predictable, subject to the venue’s approval.

Connect Browsers, Sensors And Displays

Build the browser interface with responsive HTML and JavaScript so it works across a phone, kiosk screen or wall-mounted display. Use WebSockets when the server must send live updates, such as a visitor’s movement changing a projection. For simpler interactions, regular HTTP requests may be easier to debug and sufficient for the artwork.

Keep hardware communication behind a small service. A Python or Node.js process can read serial messages from an Arduino, listen for OSC or MIDI events and publish clean values to the web application. Validate every incoming value, set sensible timeouts and define what happens when a sensor disconnects.

Test the physical arrangement as well as the code. Bright Australian sunlight entering a gallery, reflective floors in a Brisbane venue or a long cable run in a Perth warehouse can affect sensors and screens. Label cables, secure connectors and provide a manual control mode so staff can keep the work operating if one component fails.

Make The System Recoverable

A functioning installation should recover after a power cut, accidental browser closure or router restart. Configure the server and application to launch automatically with systemd, and set display computers to open the correct URL in kiosk mode. Remove browser pop-ups, sleep settings and automatic updates that could interrupt the exhibition.

Create a known-good backup before transport. Keep a second boot drive or cloned computer ready, and record the exact IP address, startup commands and cable layout. Use a small uninterruptible power supply where appropriate, particularly for a projection system or a computer controlling several devices.

Run a long-duration test for at least one full opening day. Watch CPU temperature, memory use, disk space and network stability. In the local arts market, where a technician may be shared across several venues, clear logs and a one-page recovery procedure can save valuable setup time and reduce call-outs.

Check The Installation Before Opening

A technical run-through should include visitor behaviour, not just ideal conditions. Try repeated taps, abandoned sessions, simultaneous users and deliberately disconnected sensors. Confirm that the interface gives visible feedback and that the artwork returns to a neutral state after each interaction.

The kinetic sculpture conversation in a creator interview illustrates why physical movement and digital control need to be considered together. A web server may be stable while a motor overheats, a projector loses focus or an actuator reaches its limit, so operational safeguards belong in the design.

Opening-Day Checks

Useful Maintenance Records

When the system is stable, document the final build with photographs and a short operating guide. Treat that record as part of the artwork’s archive: it will help the next venue reproduce the experience without guessing.

Build the smallest reliable network that supports the concept, test it under real gallery conditions and keep a recoverable copy of every essential file. With those foundations in place, your installation can give visitors a seamless encounter while giving technicians a clear, practical way to keep it alive.