Hi @Cagatay_Aydin,
Yes, the single application publishing feature of ThinLinc sounds like it would suit your needs perfectly. In case you haven’t seen it yet, we have an overview of this feature here:
To answer your specific questions:
Usually it is better to set up a dedicated single-app profile. This process is outlined here:
When Chromium closes, provided it is the only application running in the session, the session will be ended completely.
The users’ home directory should be sufficient for this, provided each session has a unique username and home directory.
As discussed in the knowledge base articles linked above, tl-single-app will only start the application provided to it as an argument, nothing else. This means no taskbar, menus, or any other desktop environment components. This is generally sufficient to prevent users from accessing other applications or files.
Regarding installing browser extensions, downloads, protocol handlers, file associations, etc, this would need to be configured via Chromium policies.
Assuming you don’t require features like local drive export, printing, audio, etc, the browser client should be fine. You may find that the native client gives slightly better performance, but for the use-case you describe, the difference is probably negligable.
If you have a GPU available, you could try using VirtualGL, but it may not be required for simple websites. One catch with VirtualGL is that while it’s possible to share a GPU across multiple users, it’s not possible to restrict how much of the GPU is available per user. So potentially, one user doing GPU-heavy work could affect the performance of other users on the server. So unless you really need it, it’s probably a good idea to test first without VirtualGL.
Hope that helps! Let us know how you get on with your evaluation.