Feature #33049

Allow configuration of context without environment variable (needed for IIS)

Added by Daniel Felix almost 10 years ago. Updated over 9 years ago.

Status:
New
Priority:
Could have
Assignee:
-
Category:
Core
Target version:
-
Start date:
2012-01-08
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

Hi there,

I found some configuration in some of the Framework Packages corresponding the persistence:core:context. The comment just says that this should be set by the enviroment.

This is quite a good idea, but just for Apache Users. I tried FLOW3 on IIS, and as you self wrote on your Kickstart Tutorial - you haven't tested it on IIS.

Well the point is... IIS doesn't support VirtualHosts, so there is no way for me to define the needed context.

I've done a workaround and added a line of code to the Web/index.php

putenv("FLOW3_CONTEXT=Development")

But this won't be a great deal if i have a config like the core:context.

Maybe you could give this setting in the global Settings.yaml a try.

#1

Updated by Rens Admiraal over 9 years ago

Just some extra info related to this issue:

On http://www.iis.net/ConfigReference/system.webServer/fastCgi/application/environmentVariables you can find documentation how you can set environment variables using Microsoft Administration Pack for IIS 7.0 (http://www.iis.net/expand/AdministrationPack).

This still seems to be a global setting for the entire IIS server though.

#2

Updated by Karsten Dambekalns over 9 years ago

  • Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow
#3

Updated by Karsten Dambekalns over 9 years ago

  • Tracker changed from Bug to Feature
#4

Updated by Karsten Dambekalns over 9 years ago

  • Subject changed from reactivate core:context for iis to Allow configuration of context without environment variable (needed for IIS)
  • Category set to Core
  • Priority changed from Should have to Could have
  • Has patch set to No

Also available in: Atom PDF