You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For support and general questions and discussions, please visit the [support Discord server](https://discord.gg/U4JZfsu)! Please do not use the issue tracker for general support questions. Please also remember that unless explicitly stated otherwise/you have hired services to that end, all support is free and offered on a volunteer basis, and there is no guarantee or obligation upon maintainers and/or community members to provide support.
4
+
5
+
The following are accepted uses for the [issue tracker](https://github.com/corowne/Lorekeeper/issues):
6
+
- Bug reports
7
+
- Feature or enhancement requests (within reason)-- note that these may be denied if they are deemed out of scope of the project and/or are not feasible to implement for any reason.
8
+
9
+
## Opening an Issue
10
+
### Reporting a bug
11
+
12
+
File bugs in the [issue tracker](https://github.com/corowne/Lorekeeper/issues). Please follow these guidelines:
13
+
14
+
- Search existing issues first! Make sure your issue hasn't already been reported.
15
+
- Stay on topic, but describe the issue in detail so that others can reproduce it.
16
+
- Don't use one issue for multiple bugs! Keeping them 1:1 helps with tracking and fixing problems. Similarly, don't make multiple issues for one bug.
17
+
- Provide screenshot(s) if possible.
18
+
19
+
### Feature requests
20
+
21
+
It's recommended to discuss potential new features in the [support Discord](https://discord.gg/U4JZfsu) before creating an issue, as this helps check that it is valid for a feature request and if it would be useful to others-- something which increases its likelihood of being implemented. Please also check that your request has not already been posted on the [issue tracker](https://github.com/corowne/Lorekeeper/issues).
22
+
23
+
Avoid listing multiple requests in one issue. One issue per request makes it easier to track and discuss it. If need be, you may make multiple issues (within reason), but do not spam. Do not make multiple issues for the same request.
24
+
25
+
## Contributing Code
26
+
27
+
Please see the full [Contribution Guide](http://wiki.lorekeeper.me/index.php?title=Contributing_to_Lorekeeper) for more information!
28
+
29
+
### About abandoned pull requests
30
+
31
+
In the case where a pull request is started but not finished and the contributor is nonresponsive despite efforts to contact them, the pull request will be closed regardless of its status. It is up to contributors to finish work, make any requested changes, etc., not maintainers.
32
+
33
+
However, knowledge from the issue and/or pull request may be used to create a new pull request, potentially based on the changes from the closed pull request.
Copy file name to clipboardExpand all lines: README.md
+8-12Lines changed: 8 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
3
3
Lorekeeper is a framework for managing deviantART-based ARPGs/closed species masterlists coded using the Laravel framework. In simple terms - you will be able to make a copy of the site, do some minor setup/enter data about your species and game, and it'll provide you with the automation to keep track of your species, players and ARPG submissions.
@@ -19,11 +19,11 @@ Wiki for users: [http://lorekeeper-arpg.wikidot.com/](http://lorekeeper-arpg.wik
19
19
- Speaking of which, you can search for characters based on traits, rarity, etc. Also, trait/item/etc. data get their own searchable lists - no need to create additional pages detailing restrictions on how a trait should be drawn/described.
20
20
- Unless you want to, in which case you can add custom pages in HTML without touching the codebase!
21
21
- A raffle roller for consecutive raffles! Mods can add/remove tickets and users who have already won something will be automatically removed from future raffles in the sequence.
22
-
- ...and more! Please refer to the [Wiki](http://lorekeeper-arpg.wikidot.com/) for more information and instructions for usage.
22
+
- ...and more! Please refer to the [Wiki](http://wiki.lorekeeper.me/index.php?title=Category:Documentation) for more information and instructions for usage.
23
23
24
24
# Setup
25
25
26
-
Important: For those who are not familiar with web dev, please refer to the [Wiki](http://lorekeeper-arpg.wikidot.com/) for a much more detailed set of instructions!!
26
+
Important: For those who are not familiar with web dev, please refer to the [Wiki](http://wiki.lorekeeper.me/index.php?title=Tutorial:_Setting_Up) for a much more detailed set of instructions!!
deviantART client ID and secret are required for this step.
41
-
While obtaining the ID and secret, also add whitelist entries for redirection for your site URL (if being hosted) or localhost (if working locally).
40
+
Client ID and secret for at least one supported social media platform are required for this step. See [the Wiki](http://wiki.lorekeeper.me/index.php?title=Category:Social_Media_Authentication) for platform-specific instructions.
41
+
42
42
Add the following to .env, filling them in as required (also fill in the rest of .env where relevant):
43
43
```
44
44
CONTACT_ADDRESS=(contact email address)
45
45
DEVIANTART_ACCOUNT=(username of ARPG group account)
46
-
47
-
DEVIANTART_CLIENT_ID=(client ID as supplied by deviantART)
48
-
DEVIANTART_CLIENT_SECRET=(client secret as supplied by deviantART)
49
-
DEVIANTART_CALLBACK_URL=/
50
46
```
51
47
52
48
## Setting up
@@ -74,8 +70,8 @@ Finally, set up the admin account for logging in:
74
70
$ php artisan setup-admin-user
75
71
```
76
72
77
-
You will need to send yourself the verification email and then link your dA account as prompted.
73
+
You will need to send yourself the verification email and then link your social media account as prompted.
78
74
79
75
## Contact
80
76
81
-
If you have any questions, please feel free to contact me through email: corowne@gmail.com
77
+
If you have any questions, please feel free to contact me through email: corowne@gmail.com
'description' => '0: Registration closed, 1: Registration open. When registration is closed, invitation keys can still be used to register.'
54
-
]
72
+
$this->addSiteSetting('is_registration_open', 1, '0: Registration closed, 1: Registration open. When registration is closed, invitation keys can still be used to register.');
'description' => '0: New prompt submissions cannot be made (mods can work on the queue still), 1: Prompts are submittable.'
93
-
]
78
+
$this->addSiteSetting('is_prompts_open', 1, '0: New prompt submissions cannot be made (mods can work on the queue still), 1: Prompts are submittable.');
'description' => 'Who can view the blacklist? 0: Admin only, 1: Staff only, 2: Members only, 3: Public.'
145
-
]
86
+
$this->addSiteSetting('is_design_updates_open', 1, '0: Characters cannot be submitted for design update approval, 1: Characters can be submitted for design update approval.');
'description' => 'Optional key to view the blacklist. Enter "0" to not require one.'
171
-
]
90
+
$this->addSiteSetting('blacklist_link', 0, '0: No link to the blacklist is displayed anywhere, 1: Link to the blacklist is shown on the user list.');
172
91
173
-
]);
174
-
$this->info("Added: blacklist_key / Default: 0");
175
-
}
176
-
else$this->line("Skipped: blacklist_key");
92
+
$this->addSiteSetting('blacklist_key', 0, 'Optional key to view the blacklist. Enter "0" to not require one.');
93
+
94
+
$this->addSiteSetting('design_votes_needed', 3, 'Number of approval votes needed for a design update or MYO submission to be considered as having approval.');
95
+
96
+
$this->addSiteSetting('admin_user', 1, 'ID of the site\'s admin user.');
0 commit comments